[
https://issues.apache.org/jira/browse/HBASE-20220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406309#comment-16406309
]
Hudson commented on HBASE-20220:
--------------------------------
Results for branch master
[build #267 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/267/]: (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/267//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/267//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/267//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> [RSGroup] Check if table exists in the cluster before moving it to the
> specified regionserver group
> ---------------------------------------------------------------------------------------------------
>
> Key: HBASE-20220
> URL: https://issues.apache.org/jira/browse/HBASE-20220
> Project: HBase
> Issue Type: Bug
> Components: rsgroup
> Affects Versions: 3.0.0
> Reporter: Guangxu Cheng
> Assignee: Guangxu Cheng
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20220.master.001.patch,
> HBASE-20220.master.002.patch
>
>
> move_tables_rsgroup/move_servers_tables_rsgroup can move non-existent tables
> in the cluster to the specified regionserver group successfully.It's not
> reasonable.We should check whether the table has already existed in the
> cluster before moving the table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
