hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10934) Provide HBaseAdminInterface to abstract HBaseAdmin
Date Mon, 14 Apr 2014 15:22:17 GMT

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

Carter commented on HBASE-10934:

[~ndimiduk] I've incorporated all of your suggestions.  Thanks!

Do you think we should keep getMasterCoprocessors() in the interface?  It's just a straight
delegate to getClusterStatus().getMasterCoprocessors() and doesn't seem to add much value

> Provide HBaseAdminInterface to abstract HBaseAdmin
> --------------------------------------------------
>                 Key: HBASE-10934
>                 URL: https://issues.apache.org/jira/browse/HBASE-10934
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Carter
>            Priority: Blocker
>              Labels: patch
>             Fix For: 0.99.0
>         Attachments: HBASE_10934.patch
> As HBaseAdmin is essentially the administrative API, it would seem to follow Java best
practices to provide an interface to access it instead of requiring applications to use the
raw object.
> I am proposing (and would be happy to develop):
>  * A new interface, HBaseAdminInterface, that captures the signatures of the API (HBaseAdmin
will implement this interface)
>  * A new method, HConnection.getHBaseAdmin(), that returns an instance of the interface

This message was sent by Atlassian JIRA

View raw message