Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 15 Nov 2012 18:38:13 +0000 (UTC)
From: "Varun Sharma (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1246427007.120295.1353004693881.JavaMail.jiratomcat@arcas>
In-Reply-To: <764868728.63748.1351902251865.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-7093) Couple Increments/Appends with
 Put/Delete(s)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498221#comment-13498221 ] 

Varun Sharma commented on HBASE-7093:
-------------------------------------

Hi Andrew,

I remember seeing your other JIRA which talks about the incompatibility b/w Increment and Mutation - I can't find it now but it looks like doing Increment would be harder so i might not cover that in this JIRA (only cover Append here).
                
> Couple Increments/Appends with Put/Delete(s)
> --------------------------------------------
>
>                 Key: HBASE-7093
>                 URL: https://issues.apache.org/jira/browse/HBASE-7093
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.96.0
>            Reporter: Varun Sharma
>            Assignee: Varun Sharma
>         Attachments: 7093-v1.txt
>
>
> See related issue - https://issues.apache.org/jira/browse/HBASE-4583
> Currently, we cannot bundle increment/append with put/delete operations. The above JIRA MVCC'izes the increment/append operations.
> One issue is that increment(s)/append(s) are not idempotent and hence repeating the transaction has an associated issue of leading to incorrect value/append results. This could be solved by passing additional tokens as part of the append(s).
> One possible high level approach could be:
> 1) Class IncrementMutation which inherits from Increment and Mutation
> 2) In the mutateRow call, we add a case for "IncrementMutation" object
> 3) Factor out the code wrapped inside the "lock and MVCC" from increment() function to internalIncrement.
> 4) Call internalIncrement from mutateRow and increment()

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira