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

Hudson commented on HBASE-22279:
--------------------------------

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

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/953//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/master/953//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/953//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


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


> Add a getRegionLocator method in Table/AsyncTable interface
> -----------------------------------------------------------
>
>                 Key: HBASE-22279
>                 URL: https://issues.apache.org/jira/browse/HBASE-22279
>             Project: HBase
>          Issue Type: Improvement
>          Components: asyncclient, Client
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>
> As it is used in shell, for now we just call the getRegionLocator method in 
> HTable.



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

Reply via email to