[
https://issues.apache.org/jira/browse/HBASE-17953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981307#comment-15981307
]
Zheng Hu commented on HBASE-17953:
----------------------------------
If create a new table with VERSION =3 ，and the user start a VerifyReplication
job without setting versions option (newcomer did not realize that he need to
set versions option) , then the job just verify the lastest version.
Furthermore, we have the following javadoc but only verify the lastest version
by default.
{code}
/**
* This map-only job compares the data from a local table with a remote one.
* Every cell is compared and must have exactly the same keys (even timestamp)
* as well as same value. It is possible to restrict the job by time range and
* families. The peer id that's provided must match the one given when the
* replication stream was setup.
* <p>
* Two counters are provided, Verifier.Counters.GOODROWS and BADROWS. The reason
* for a why a row is different is shown in the map's log.
*/
{code}
> VerifyReplication should read all versions other than the latest version by
> default.
> ------------------------------------------------------------------------------------
>
> Key: HBASE-17953
> URL: https://issues.apache.org/jira/browse/HBASE-17953
> Project: HBase
> Issue Type: Bug
> Reporter: Zheng Hu
> Assignee: Zheng Hu
>
> Two problems for VerifyReplication.java:
> 1. With the default versions ( DO NOT set --versions option) , we will
> read the latest version other than all version, because Scan.maxVersions is
> 1. Actuallly, I think we should compare all version by default.
> 2. In logFailRowAndIncreaseCounter() method , we should set
> familly/TimeRange/maxVersions attrs for a Get.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
