Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 20 Apr 2012 17:32:40 +0000 (UTC)
From: "Zhihong Yu (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <241039771.10458.1334943160705.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <807147279.3203.1334781760718.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5824) HRegion.incrementColumnValue is not
 used in trunk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zhihong Yu commented on HBASE-5824:
-----------------------------------

I talked with Jimmy offline. We agree that single Put execution path isn't of high priority.
We will leave the discussion and decision making to HBASE-5845.
                
> HRegion.incrementColumnValue is not used in trunk
> -------------------------------------------------
>
>                 Key: HBASE-5824
>                 URL: https://issues.apache.org/jira/browse/HBASE-5824
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Elliott Clark
>            Assignee: Jimmy Xiang
>             Fix For: 0.96.0
>
>         Attachments: 5824-addendum-v2.txt, hbase-5824.patch, hbase-5824_v2.patch, hbase_5824.addendum
>
>
> on 0.94 a call to client.HTable#incrementColumnValue will cause HRegion#incrementColumnValue.  On trunk all calls to HTable.incrementColumnValue got to HRegion#increment.
> My guess is that HTable#incrementColumnValue and HTable#increment serialize to the same thing over the wire so that the remote HRegionServer no longer knows which htable method was called.
> To repro I checked out trunk and put a break point in HRegion#incrementColumnValue and then ran TestFromClientSide.  The breakpoint wasn't hit.

--
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