hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-333) we should have some checks that the sort benchmark generates correct outputs
Date Fri, 16 Feb 2007 10:10:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473659
] 

Hadoop QA commented on HADOOP-333:
----------------------------------

+1, because http://issues.apache.org/jira/secure/attachment/12351331/HADOOP-333_20070216_4.patch
applied and successfully tested against trunk revision r508345.

> we should have some checks that the sort benchmark generates correct outputs
> ----------------------------------------------------------------------------
>
>                 Key: HADOOP-333
>                 URL: https://issues.apache.org/jira/browse/HADOOP-333
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>         Assigned To: Arun C Murthy
>         Attachments: HADOOP-333_20070213_1.patch, HADOOP-333_20070214_2.patch, HADOOP-333_20070215_3.patch,
HADOOP-333_20070216_4.patch
>
>
> We should implement some checks of the input versus output of the sort benchmark to get
some correctness guarantees:
> 1. the number of records
> 2. the number of bytes
> 3. the output records are in fact sorted
> 4. the xor of the md5 of each record's key/value pair

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message