You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2014/04/18 19:41:19 UTC

[jira] [Updated] (HBASE-10934) Provide Admin interface to abstract HBaseAdmin

     [ https://issues.apache.org/jira/browse/HBASE-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enis Soztutar updated HBASE-10934:
----------------------------------

    Summary: Provide Admin interface to abstract HBaseAdmin  (was: Provide Admin to abstract HBaseAdmin)

> Provide Admin interface to abstract HBaseAdmin
> ----------------------------------------------
>
>                 Key: HBASE-10934
>                 URL: https://issues.apache.org/jira/browse/HBASE-10934
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Carter
>            Assignee: Carter
>            Priority: Blocker
>              Labels: patch
>             Fix For: 0.99.0
>
>         Attachments: HBASE_10934.patch, HBASE_10934_2.patch, HBASE_10934_3.patch, HBASE_10934_4.patch, HBASE_10934_5.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)