Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <11645166.431051279321912352.JavaMail.jira@thor>
Date: Fri, 16 Jul 2010 19:11:52 -0400 (EDT)
From: "ryan rawson (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Resolved: (HBASE-2553) Revisit IncrementColumnValue
 implementation in 0.22
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ryan rawson resolved HBASE-2553.
--------------------------------

     Hadoop Flags: [Reviewed]
    Fix Version/s: 0.90.0
                       (was: 0.92.0)
       Resolution: Fixed

committed

> Revisit IncrementColumnValue implementation in 0.22
> ---------------------------------------------------
>
>                 Key: HBASE-2553
>                 URL: https://issues.apache.org/jira/browse/HBASE-2553
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ryan rawson
>            Assignee: ryan rawson
>             Fix For: 0.90.0
>
>
> right now we are using too much of the old get code, we need to review that and constrain how this works but without breaking ICV.
> Also we should be resetting the timestamp on every ICV call, and removing the older version.  Instead of 'updating' an ICV "in place" we should be adding a new one, removing the old one from memstore (if it is there).  This will play well with the atomic approach added in HBASE-2248 since we are only touching 1 KeyValue at a time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.