[
https://issues.apache.org/jira/browse/HADOOP-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512760
]
Hadoop QA commented on HADOOP-1614:
-----------------------------------
+1
http://issues.apache.org/jira/secure/attachment/12361841/patch.txt applied and
successfully tested against trunk revision r556348.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/416/testReport/
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/416/console
> [hbase] HClient does not protect itself from simultaneous updates
> -----------------------------------------------------------------
>
> Key: HADOOP-1614
> URL: https://issues.apache.org/jira/browse/HADOOP-1614
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.15.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Fix For: 0.15.0
>
> Attachments: patch.txt
>
>
> HClient.startUpdate establishes a lot of state for subsequent put, delete,
> commit and abort calls. If startUpdate is called a second time before the
> first update is committed or aborted, it could easily cause the first update
> to fail if the row associated with the second update was on a different
> region server, for example.
> Similarly, openTable could destroy the state if it were called after a
> startUpdate and prior to a commit or abort.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
