hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-748) Add an efficient way to batch update many rows
Date Tue, 09 Sep 2008 22:27:45 GMT

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

Jean-Daniel Cryans commented on HBASE-748:

If we are to batch any row operation, I think we will need to create a new class for gets.
I don't think a signature like that is what we want:

public RowResult getRow(final byte [][] row, final byte [][][] columns, final long[] ts, final
RowLock[] rl) 

In fact, a class that looks like BatchUpdate would be what we need. Thinking of it, we could
drop many of the ever expanding client API methods using such a class. I would also put the
row lock inside that class.

Finally, it would be used by the row-batching logic (which is worst to design than I thought
it was at first) as a generic row operation.

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

View raw message