[
https://issues.apache.org/jira/browse/HBASE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634884#action_12634884
]
Jean-Daniel Cryans commented on HBASE-748:
------------------------------------------
{quote}
Should the RowLock be associated with the BatchUpdate rather than being
supplied on commit? That would allow us to remove one commit overload, and
allow the client to associate the row lock with multiple BatchUpdates for the
same row.
{quote}
This is in the scope of HBASE-880. Glad to see that I'm not the only one who
saw that problem.
bq. +1 on moving checks into commit (or flushCommits).
That would be in commit since in flush it's too late IMO.
> Add an efficient way to batch update many rows
> ----------------------------------------------
>
> Key: HBASE-748
> URL: https://issues.apache.org/jira/browse/HBASE-748
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: client
> Affects Versions: 0.1.3, 0.2.0
> Reporter: Jean-Daniel Cryans
> Assignee: Jean-Daniel Cryans
> Fix For: 0.19.0
>
> Attachments: hbase-748-v1.patch
>
>
> HBASE-747 introduced a simple way to batch update many rows. The goal of this
> issue is to have an enhanced version that will send many rows in a single RPC
> to each region server. To do this, the client code will have to figure which
> rows goes to which server, group them accordingly and then send them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
