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

Hudson commented on HBASE-21762:
--------------------------------

Results for branch branch-2
        [build #1636 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1636/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1636//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1636//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1636//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Move some methods in ClusterConnection to Connection
> ----------------------------------------------------
>
>                 Key: HBASE-21762
>                 URL: https://issues.apache.org/jira/browse/HBASE-21762
>             Project: HBase
>          Issue Type: Task
>          Components: Client
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0
>
>         Attachments: HBASE-21762-v1.patch, HBASE-21762.patch
>
>
> For example, clearRegionCache, getHbck, etc. The getHbck method will be 
> marked as IA.LimitedPrivate to indicate that normal user should not use it. 
> And I think this is OK, as it is not easy to use the Hbck interface directly, 
> and the name 'hbck' also implies that it should not be used for normal case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to