You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/07/02 19:18:05 UTC

[jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes

     [ https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey updated HBASE-13561:
--------------------------------
    Fix Version/s:     (was: 1.2.0)
                   1.2.1
                   1.3.0

still working on this?

> 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.14, 1.0.2, 1.1.2, 1.3.0, 1.2.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)