[
https://issues.apache.org/jira/browse/HBASE-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966794#comment-13966794
]
Nick Dimiduk commented on HBASE-10934:
--------------------------------------
Looks like you're on the right track. Let me ask of the wider audience: do we
want to cary forward the {{@Deprecated}} methods into this interface? I think
not. I also wonder about all these exceptions; are there places where we can
fold them together? Basically, how to we minimize the surface area of this
interface?
A nit: for convenience methods like {{tableExists(String)}},
{{tableExists(byte[])}}, please include a javadoc {{@see}} reference back to
the method that does the work, {{tableExists(TableName)}}.
> 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
(v6.2#6252)
