[
https://issues.apache.org/jira/browse/HBASE-20378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443501#comment-16443501
]
Hadoop QA commented on HBASE-20378:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} HBASE-20378 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-20378 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12919745/HBASE-20378.master.004.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/12551/console |
| Powered by | Apache Yetus 0.7.0 http://yetus.apache.org |
This message was automatically generated.
> Provide a hbck option to cleanup replication barrier for a table
> ----------------------------------------------------------------
>
> Key: HBASE-20378
> URL: https://issues.apache.org/jira/browse/HBASE-20378
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 3.0.0
> Reporter: Duo Zhang
> Assignee: Jingyun Tian
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20378.master.001.patch,
> HBASE-20378.master.002.patch, HBASE-20378.master.003.patch,
> HBASE-20378.master.004.patch
>
>
> It is not easy to deal with the scenario where a user change the replication
> scope from global to local since it may change the scope back while we are
> cleaning in the background. And I think this a rare operation so just provide
> an hbck option to deal with it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
