[
https://issues.apache.org/jira/browse/HBASE-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096429#comment-16096429
]
stack commented on HBASE-17822:
-------------------------------
[~zhangshibin] Do you get the review comments by [~yangzhe1991]? He suggests,
and I agree, that you should not change the default behavior which is to spew
all bad rows without limit and not write to an output file? Does that make
sense?
> Set maxBadRows and outputDirectory option for VerifyReplication
> ----------------------------------------------------------------
>
> Key: HBASE-17822
> URL: https://issues.apache.org/jira/browse/HBASE-17822
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Reporter: Shibin Zhang
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: 2017-06-30_110905.png, 2017-06-30_110915.png,
> HBASE-17822-master.patch, HBASE-17822-V1.patch
>
>
> Currently,this tool will print too many rowkey as badrows if source and peer
> table have many inconsistent row.So,it is necessay to set maxBadRows to print.
> Also,look for badrows rowkey is inconvenient in MR job log .It might be
> useful to set a reduce to aggregate badrowkeys which will be print in MR job
> output file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
