[
https://issues.apache.org/jira/browse/HBASE-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645639#comment-15645639
]
Hudson commented on HBASE-17026:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-1.4 #522 (See
[https://builds.apache.org/job/HBase-1.4/522/])
HBASE-17026 VerifyReplication log should distinguish whether good row (tedyu:
rev ecd4de938b44b8d1edeadbc2204678828ef18072)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java
> VerifyReplication log should distinguish whether good row key is result of
> revalidation
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-17026
> URL: https://issues.apache.org/jira/browse/HBASE-17026
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Fix For: 2.0.0, 1.4.0
>
> Attachments: 17026.v1.txt, 17026.v2.txt
>
>
> Inspecting app log from VerifyReplication, I saw lines in the following form:
> {code}
> 2016-11-03 15:28:44,877 INFO [main]
> org.apache.hadoop.hbase.mapreduce.replication.VerifyReplication: Good row
> key: X000 X
> {code}
> where 'X' is the delimiter.
> Without line number, it is difficult to tell whether the good row has gone
> through revalidation.
> This issue is to distinguish the two logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
