You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2007/07/14 18:09:04 UTC

[jira] Work started: (HADOOP-1614) [hbase] HClient does not protect itself from simultaneous updates

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

Work on HADOOP-1614 started by Jim Kellerman.

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