[
https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785982#comment-16785982
]
Hudson commented on HBASE-21871:
--------------------------------
Results for branch branch-2
[build #1732 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1732/]:
(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/branch-2/1732//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/branch-2/1732//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1732//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1732//console].
> Support to specify a peer table name in VerifyReplication tool
> --------------------------------------------------------------
>
> Key: HBASE-21871
> URL: https://issues.apache.org/jira/browse/HBASE-21871
> Project: HBase
> Issue Type: Improvement
> Reporter: Toshihiro Suzuki
> Assignee: Subrat Mishra
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0, 2.1.4
>
> Attachments: HBASE-21871.master.001.patch,
> HBASE-21871.master.002.patch, HBASE-21871.master.002.patch
>
>
> After HBASE-21201, we can specify peerQuorumAddress instead of peerId in
> VerifyReplication tool. So it no longer requires peerId to be setup when
> using this tool. However, we don't have a way to specify a peer table name in
> VerifyReplication for now.
> So I would like to propose to update the tool to pass as a peer table name as
> an argument (ex. --peerTableName=<tablename>).
> After resolving this Jira, we will be able to compare any 2 tables in any
> remote clusters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
