hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (HBASE-880) Improve the current client API by creating new container classes
Date Tue, 30 Sep 2008 20:25:46 GMT

    [ https://issues.apache.org/jira/browse/HBASE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635823#action_12635823
] 

jimk edited comment on HBASE-880 at 9/30/08 1:24 PM:
--------------------------------------------------------------

This diagram essentially is my proposal in the interest of time, I did not redo scanners yet,
nor did I address Stack's latest comments.

Note that I removed the deprecated methods from HTable so we could see what the eventual API
looks like without all the other clutter.

I will address Stack's comments in a separate comment.

      was (Author: jimk):
    This diagram essentially is my proposal in the interest of time, I did not redo scanners
yet, nor did I address Stack's latest comments.

I will address Stack's comments in a separate comment.
  
> 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: hbase-880-patch.jpg, hbase-880-v1.patch, hbase-880-v2.patch, hbase_client_classes.png,
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.


Mime
View raw message