Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0AE6E9D5A for ; Fri, 13 Jan 2012 06:48:24 +0000 (UTC) Received: (qmail 24749 invoked by uid 500); 13 Jan 2012 06:48:23 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 23286 invoked by uid 500); 13 Jan 2012 06:48:04 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 23262 invoked by uid 99); 13 Jan 2012 06:48:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jan 2012 06:48:01 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jan 2012 06:48:00 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 20B9E1492C4 for ; Fri, 13 Jan 2012 06:47:40 +0000 (UTC) Date: Fri, 13 Jan 2012 06:47:40 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: issues@hbase.apache.org Message-ID: <343977955.37234.1326437260141.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <585229115.3711.1298944296934.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HBASE-3584) We need to atomically put/delete/increment in one call MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185459#comment-13185459 ] Hadoop QA commented on HBASE-3584: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12510460/3584-v3.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 9 new or modified tests. -1 javadoc. The javadoc tool appears to have generated -147 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 82 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface org.apache.hadoop.hbase.mapreduce.TestImportTsv org.apache.hadoop.hbase.mapred.TestTableMapReduce org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/752//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/752//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/752//console This message is automatically generated. > We need to atomically put/delete/increment in one call > ------------------------------------------------------ > > Key: HBASE-3584 > URL: https://issues.apache.org/jira/browse/HBASE-3584 > Project: HBase > Issue Type: Bug > Components: client, coprocessors, regionserver > Reporter: ryan rawson > Assignee: Lars Hofhansl > Fix For: 0.94.0 > > Attachments: 3584-v1.txt, 3584-v3.txt > > > Right now we have the following calls: > put(Put) > delete(Delete) > increment(Increments) > But we cannot combine all of the above in a single call, complete with a single row lock. It would be nice to do that. > It would also allow us to do a CAS where we could do a put/increment if the check succeeded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira