[
https://issues.apache.org/jira/browse/HBASE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629920#action_12629920
]
stack commented on HBASE-880:
-----------------------------
Suggest RowUpdate instead of RowMutation or BatchUpdate. Goes better with
RowGet than RowMutation, IMO.
Regards the below...
{code}
RowResult[] results = htable.get(batch); // or maybe a SortedMap?
{code}
... we should make htable.get so it can take a List of RowGets or a single
RowGet (should fail on RowOperation). Or maybe we should add a getBatch that
takes a List and returns SortedMap whereas get takes single RowGet and returns
a RowResult.
RowGet should take columns in its constructor. Should be immutable type.
> Improve the current client API by creating new container classes
> ----------------------------------------------------------------
>
> Key: HBASE-880
> URL: https://issues.apache.org/jira/browse/HBASE-880
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: client
> Reporter: Jean-Daniel Cryans
> Fix For: 0.19.0
>
>
> The current API does not scale very well. For each new feature, we have to
> add many methods to take care of all the overloads. Also, the need to batch
> row operations (gets, inserts, deletes) implies that we have to manage some
> "entities" like we are able to do with BatchUpdate but not with the other
> operations. The RowLock should be an attribute of such an entity.
> The scope of this jira is only to replace current API with another
> feature-compatible one, other methods will be added in other issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
