[
https://issues.apache.org/jira/browse/HBASE-5824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258313#comment-13258313
]
Zhihong Yu commented on HBASE-5824:
-----------------------------------
In 0.94, client only needs to deal with RetriesExhaustedWithDetailsException
whose only cause is a ConstraintException
With Jimmy's patch, client needs to deal with
RetriesExhaustedWithDetailsException (not subclass of DoNotRetryIOException)
and ConstraintException (subclass of DoNotRetryIOException). This is because
there're two execution paths for Put.
I am afraid Benoit would have more to complain about in HBASE-5796 :-)
> 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: 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
