hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10934) Provide HBaseAdminInterface to abstract HBaseAdmin
Date Wed, 16 Apr 2014 16:48:19 GMT

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

Nick Dimiduk commented on HBASE-10934:
--------------------------------------

bq. Do you think we should keep getMasterCoprocessors() in the interface?

I have no opinion about this.

[~apurtell], [~enis], [~stack], thoughts?

> 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, HBASE_10934_2.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
(v6.2#6252)

Mime
View raw message