[
https://issues.apache.org/jira/browse/HBASE-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974094#comment-13974094
]
Hadoop QA commented on HBASE-10934:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12640818/HBASE_10934_4.patch
against trunk revision .
ATTACHMENT ID: 12640818
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9332//console
This message is automatically generated.
> 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,
> HBASE_10934_3.patch, HBASE_10934_4.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)
