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

Hudson commented on HBASE-20210:
--------------------------------

Results for branch master
        [build #263 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/263/]: (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/master/263//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/263//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/263//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


> Note in refguide that RSGroups API is private, not for public consumption; 
> shell is only access
> -----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-20210
>                 URL: https://issues.apache.org/jira/browse/HBASE-20210
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 2.0.0
>
>         Attachments: HBASE-20210.master.001.patch
>
>
> Came up yesterday in an internal conversation. Mike Drob noticed that the 
> CPEP for RSGroups is marked audience Private which sort of makes sense given 
> this an evolving feature. The refguide though makes it sound as though you 
> can drive RSGroups from shell or API. Let me shutdown the talk of API being 
> public.



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

Reply via email to