Hudson commented on HBASE-24032:

Results for branch branch-2.3
        [build #7 on 
(x) *{color:red}-1 overall{color}*
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 

(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 

(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 

(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 

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

(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for 
 (note that this means we didn't run on Hadoop 3)

> [RSGroup] Assign created tables to respective rsgroup automatically instead 
> of manual operations 
> -------------------------------------------------------------------------------------------------
>                 Key: HBASE-24032
>                 URL: https://issues.apache.org/jira/browse/HBASE-24032
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, rsgroup
>            Reporter: Reid Chan
>            Assignee: Reid Chan
>            Priority: Major
>             Fix For: 2.3.0, master, 1.7.0, 1.4.14, 2.2.5
> In prod practise, it's time consuming and tiring to assign tables to their 
> rsgroups for HBase admin by shell, especially in 1.x rsgroup client is 
> IA.private, we could not even write some programs to do that.
> And I'm here proposing a solution to do the automated rsgroup assignment by 
> allowing running a shell in postCreateTable to determine which table should 
> go to which rsgroup (way in branch-1 not master). The benefit is obvious, 
> admin can determine or change at any time the mapping rule in script without 
> restarting or re-config anything. It's flexible, convenience and time saving.

This message was sent by Atlassian Jira

Reply via email to