[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[
https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786043#comment-16786043
]
Hudson commented on HBASE-21871:
Results for branch branch-2.1
[build #927 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/927/]:
(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.1/927//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.1/927//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.1/927//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.1/927//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=).
> 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[
https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786015#comment-16786015
]
Hudson commented on HBASE-21871:
Results for branch master
[build #844 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/844/]: (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/844//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/844//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/844//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/master/844//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=).
> 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[
https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785999#comment-16785999
]
Hudson commented on HBASE-21871:
Results for branch branch-2.2
[build #87 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/87/]:
(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.2/87//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.2/87//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.2/87//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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=).
> 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[
https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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=).
> 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[ https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785693#comment-16785693 ] Toshihiro Suzuki commented on HBASE-21871: -- Pushed to master, branch-2, branch-2.1 and branch-2.2. Thank you for contributing! [~subrat.mishra] > 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=). > 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[ https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785678#comment-16785678 ] Toshihiro Suzuki commented on HBASE-21871: -- Looks good to me. Let me commit. > 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 > 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=). > 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[
https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785212#comment-16785212
]
Hadoop QA commented on HBASE-21871:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 2m
26s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
30s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
40s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
30s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
36s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 2m
30s{color} | {color:blue} hbase-server in master has 1 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
44s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
34s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
8m 44s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
46s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}134m
9s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 14m
33s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
47s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}196m 27s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-21871 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12961268/HBASE-21871.master.002.patch
|
| Optional Tests | dupname asflicense javac javadoc unit findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 6d2a51dc0dad 4.4.0-137-generic #163~14.04.1-Ubuntu SMP Mon Sep
24 17:14:57 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / 4a78deb616 |
| maven | version: Apache Maven 3.5.4
(1edded0938998edf8bf061f1ceb3cfdeccf443fe;
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[
https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784429#comment-16784429
]
Hadoop QA commented on HBASE-21871:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
28s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
13s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
21s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 3m
3s{color} | {color:blue} hbase-server in master has 1 extant Findbugs warnings.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
55s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 3m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 3m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
40s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
10m 23s{color} | {color:green} Patch does not cause any errors with Hadoop
2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
55s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}321m 20s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 26m
20s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
48s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}401m 30s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.tool.TestSecureLoadIncrementalHFiles |
| | hadoop.hbase.master.procedure.TestSCPWithReplicasWithoutZKCoordinated |
| | hadoop.hbase.client.TestSnapshotTemporaryDirectory |
| | hadoop.hbase.client.replication.TestReplicationAdminWithClusters |
| | hadoop.hbase.client.TestSnapshotDFSTemporaryDirectory |
| | hadoop.hbase.client.TestFromClientSideWithCoprocessor |
| | hadoop.hbase.master.procedure.TestSCPWithReplicas |
| | hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas |
| | hadoop.hbase.client.TestAsyncTableAdminApi |
| | hadoop.hbase.util.TestFromClientSide3WoUnsafe |
| | hadoop.hbase.tool.TestLoadIncrementalHFiles |
| | hadoop.hbase.client.TestFromClientSide3 |
| |
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[ https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784153#comment-16784153 ] Subrat Mishra commented on HBASE-21871: --- Thanks [~brfrn169] for the review. > 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 > Attachments: HBASE-21871.master.001.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=). > 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[ https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783771#comment-16783771 ] Toshihiro Suzuki commented on HBASE-21871: -- [~subrat.mishra] LGTM +1 > 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 > Attachments: HBASE-21871.master.001.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=). > 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[ https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783261#comment-16783261 ] Subrat Mishra commented on HBASE-21871: --- Hi [~brfrn169], Thanks for assigning to me. Can you please review the patch? I will correct the checkstyle after the review. > 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 > Attachments: HBASE-21871.master.001.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=). > 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)
[jira] [Commented] (HBASE-21871) Support to specify a peer table name in VerifyReplication tool
[
https://issues.apache.org/jira/browse/HBASE-21871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783233#comment-16783233
]
Hadoop QA commented on HBASE-21871:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
29s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
48s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
31s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
34s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 2m
38s{color} | {color:blue} hbase-server in master has 1 extant Findbugs
warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
48s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
41s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
19s{color} | {color:red} hbase-mapreduce: The patch generated 8 new + 17
unchanged - 0 fixed = 25 total (was 17) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
41s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
9m 0s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}152m
8s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 19m
37s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
50s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}220m 2s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:b002b0b |
| JIRA Issue | HBASE-21871 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12960949/HBASE-21871.master.001.patch
|
| Optional Tests | dupname asflicense javac javadoc unit findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 902cde114e99 4.4.0-139-generic #165~14.04.1-Ubuntu SMP Wed Oct
31 10:55:11 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | master / c9804758d1 |
| maven | version: Apache
