[
https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522716#comment-14522716
]
Josh Elser commented on HBASE-13561:
------------------------------------
bq. I think if UNDEFINED is not zero, it is a problem, right? Job should fail?
Yes, that's what I believe is the best course of action. Just wanted to double
check that I wasn't missing something that was just some norm.
> ITBLL.Verify doesn't actually evaluate counters after job completes
> -------------------------------------------------------------------
>
> Key: HBASE-13561
> URL: https://issues.apache.org/jira/browse/HBASE-13561
> Project: HBase
> Issue Type: Bug
> Components: integration tests
> Affects Versions: 1.0.0, 2.0.0, 1.1.0, 0.98.12
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1
>
>
> Was digging through ITBLL and noticed this oddity:
> The {{Verify}} Tool doesn't actually call {{Verify#verify(long)}} like the
> {{Loop}} Tool does. Granted, it doesn't know the total number of KVs that
> were written given the current arguments, it's not even checking to see if
> there things like UNDEFINED records found.
> It seems to me that {{Verify}} should really be doing *some* checking on the
> counters like {{Loop}} does and not just leaving it up to the visual
> inspection of whomever launched the task.
> Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
