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

Hudson commented on HBASE-24654:
--------------------------------

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

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/136/General_20Nightly_20Build_20Report/]






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


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/136/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


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


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


> Allow unset table's rsgroup
> ---------------------------
>
>                 Key: HBASE-24654
>                 URL: https://issues.apache.org/jira/browse/HBASE-24654
>             Project: HBase
>          Issue Type: Improvement
>          Components: rsgroup
>    Affects Versions: 3.0.0-alpha-1
>            Reporter: Sun Xin
>            Assignee: Sun Xin
>            Priority: Major
>             Fix For: 3.0.0-alpha-1
>
>
> In TableDescriptorBuilder, we have only one method to set rsgroup, but have 
> no one to unset it. this unset method is necessary In some cases.
> If the table had rsgroup config before, but now I want to use the namespace 
> config. It doesn't work that I set table rsgroup config to default rsgroup, 
> must remove rsgroup config.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to