[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304439#comment-15304439 ] Hudson commented on HBASE-15847: FAILURE: Integrated in HBase-0.98-matrix #348 (See [https://builds.apache.org/job/HBase-0.98-matrix/348/]) HBASE-15847 VerifyReplication prefix filtering (apurtell: rev 734c50bc616cc3595f45dd212a5ff0200a5c9ea5) * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java * hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationSmallTests.java > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby > Fix For: 2.0.0, 1.4.0, 0.98.20 > > Attachments: HBASE-15847-0.98.patch, HBASE-15847-branch-1.patch, > HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304389#comment-15304389 ] Hudson commented on HBASE-15847: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1220 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1220/]) HBASE-15847 VerifyReplication prefix filtering (apurtell: rev 734c50bc616cc3595f45dd212a5ff0200a5c9ea5) * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java * hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationSmallTests.java > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby > Fix For: 2.0.0, 1.4.0, 0.98.20 > > Attachments: HBASE-15847-0.98.patch, HBASE-15847-branch-1.patch, > HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302696#comment-15302696 ] Andrew Purtell commented on HBASE-15847: Thanks [~gjacoby], I will apply it today > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-15847-0.98.patch, HBASE-15847-branch-1.patch, > HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292246#comment-15292246 ] Hudson commented on HBASE-15847: FAILURE: Integrated in HBase-1.4 #163 (See [https://builds.apache.org/job/HBase-1.4/163/]) HBASE-15847 VerifyReplication prefix filtering (Geoffrey Jacoby) (tedyu: rev 696a51d3444827426f0b32aa3dc04d5ced427d3a) * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java * hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationSmallTests.java > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-15847-branch-1.patch, HBASE-15847.patch, > HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292067#comment-15292067 ] Hudson commented on HBASE-15847: FAILURE: Integrated in HBase-Trunk_matrix #932 (See [https://builds.apache.org/job/HBase-Trunk_matrix/932/]) HBASE-15847 VerifyReplication prefix filtering (Geoffrey Jacoby) (tedyu: rev a050e1d9f84eed0b73b5f8ca30d9d93b5bf50057) * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java * hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationSmallTests.java > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby > Fix For: 2.0.0, 1.4.0 > > Attachments: HBASE-15847-branch-1.patch, HBASE-15847.patch, > HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291100#comment-15291100 ] Ted Yu commented on HBASE-15847: Mind attaching patch for branch-1 ? > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby > Attachments: HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290533#comment-15290533 ] Ashish Singhi commented on HBASE-15847: --- lgtm > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby > Attachments: HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290277#comment-15290277 ] Ted Yu commented on HBASE-15847: Planning to commit some time tomorrow if there is no further review comment. > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby > Attachments: HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289925#comment-15289925 ] Ted Yu commented on HBASE-15847: +1 > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby > Attachments: HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[
https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289914#comment-15289914
]
Hadoop QA commented on HBASE-15847:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {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 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
26s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 51s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 34s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
53s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
58s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 32s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
42s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 47s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 47s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 33s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 33s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 8m
53s {color} | {color:green} Patch does not cause any errors with Hadoop 2.4.1
2.5.2 2.6.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 32s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 99m 44s
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 124m 44s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12804540/HBASE-15847.v1.patch |
| JIRA Issue | HBASE-15847 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf900.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/yetus-0.2.1/lib/precommit/personality/hbase.sh
|
| git revision | master / 393bcd6 |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/1948/testReport/ |
| modules | C: hbase-server U: hbase-server
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289044#comment-15289044 ] Ted Yu commented on HBASE-15847: Mind re-attaching for another QA run ? > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby > Attachments: HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[
https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288041#comment-15288041
]
Hadoop QA commented on HBASE-15847:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {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 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
28s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 43s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 32s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
58s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
17s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
59s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 29s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 37s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
45s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 52s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 34s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 34s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
53s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 9m
26s {color} | {color:green} Patch does not cause any errors with Hadoop 2.4.1
2.5.2 2.6.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 30s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 35s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 92m 57s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 118m 46s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestScannerHeartbeatMessages |
| | hadoop.hbase.security.token.TestGenerateDelegationToken |
| | hadoop.hbase.regionserver.TestRegionServerMetrics |
| Timed out junit tests | org.apache.hadoop.hbase.io.hfile.TestCacheOnWrite |
| | org.apache.hadoop.hbase.io.encoding.TestEncodedSeekers |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12804540/HBASE-15847.v1.patch |
| JIRA Issue | HBASE-15847 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf906.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[
https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287867#comment-15287867
]
Hadoop QA commented on HBASE-15847:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {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 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 42s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 34s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
54s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
59s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 36s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
48s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 50s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 50s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 35s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 35s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
59s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 9m
27s {color} | {color:green} Patch does not cause any errors with Hadoop 2.4.1
2.5.2 2.6.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
13s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 32s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 100m 21s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 126m 9s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestScannerHeartbeatMessages |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12804515/HBASE-15847.patch |
| JIRA Issue | HBASE-15847 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux pietas.apache.org 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT
Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/yetus-0.2.1/lib/precommit/personality/hbase.sh
|
| git revision | master / 2c22e20 |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs | v3.0.0 |
| unit |
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287853#comment-15287853 ] Geoffrey Jacoby commented on HBASE-15847: - I already was populating with data before the first prefix, but the code wasn't as clear as it should have been that that was being done. Pushing up a patch that clarifies the before-prefix rows and adds in after-prefix rows. > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby > Attachments: HBASE-15847.patch, HBASE-15847.v1.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287754#comment-15287754 ] Ted Yu commented on HBASE-15847: For testVerifyReplicationPrefixFiltering, can you populate data with row keys before the first prefix and after the last prefix ? > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Affects Versions: 2.0.0, 0.98.19, 1.1.5 >Reporter: Geoffrey Jacoby > Attachments: HBASE-15847.patch > > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15847) VerifyReplication prefix filtering
[ https://issues.apache.org/jira/browse/HBASE-15847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287135#comment-15287135 ] Dave Latham commented on HBASE-15847: - Row or column prefixes or both? Would be better to be able to specify arbitrary Filters somehow? > VerifyReplication prefix filtering > -- > > Key: HBASE-15847 > URL: https://issues.apache.org/jira/browse/HBASE-15847 > Project: HBase > Issue Type: New Feature > Components: Replication >Reporter: Geoffrey Jacoby > > VerifyReplication currently lets a user verify data within a time range has > been replicated to a particular peer. It can be useful to verify only data > that starts with particular prefixes. (An example would be an unsalted > multi-tenant Phoenix table where you wish to only verify data for particular > tenants.) > Add a new option to the VerifyReplication job to allow for a list of prefixes > to be given. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
