hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13561) ITBLL.Verify doesn't actually evaluate counters after job completes
Date Sat, 25 Apr 2015 17:14:38 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512604#comment-14512604
] 

stack commented on HBASE-13561:
-------------------------------

I'd not noticed this. I've been doing the visual inspection w/o thinking otherwise.

> 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.0, 0.98.13, 1.0.2
>
>
> 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)

Mime
View raw message