hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
Date Tue, 07 Jul 2015 20:15:05 GMT

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

stack updated HBASE-13561:
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s:     (was: 1.0.3)
                       (was: 0.98.14)
           Status: Resolved  (was: Patch Available)

Pushed to branch-1, branch-1.1, branch-1.2, and master. Did not push to branch-1.0 or 0.98
(if you put up a backport, I'll apply to these branches too [~elserj])

> 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, 1.1.2, 1.3.0, 1.2.1
>         Attachments: HBASE-13561-v1.patch, HBASE-13561-v2.patch
> 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

View raw message