[
https://issues.apache.org/jira/browse/HBASE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652439#action_12652439
]
stack commented on HBASE-880:
-----------------------------
Patch already purged Cell of any notion of Cells.
I've made a new Cells class. Can't change RowResult because it'll break
current API. Made new Result. It has Cells.
Why should Get and Delete haveA CBM instead of inheriting? It makes things
messier.
Let me play with your last suggestion. Looks good.
> 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
> Assignee: Jean-Daniel Cryans
> Fix For: 0.19.0
>
> Attachments: 880.patch, 880proposal4plus-v2.patch,
> 880proposal4plus.patch, 880proposal5.patch, 880proposal5.png,
> hbase-880-patch.jpg, hbase-880-proposal4.patch, hbase-880-v1.patch,
> hbase-880-v2.patch, hbase_client_classes.png, NewCilentAPIProposoal4.gif,
> proposal2.jpg, proposed.jpg
>
>
> 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.
