hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4694) Inconsistency in reduce input record counters between the stable and evolving APIs
Date Mon, 01 Oct 2012 18:13:09 GMT

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

Hadoop QA commented on MAPREDUCE-4694:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12547238/MAPREDUCE-4694.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient:

                  org.apache.hadoop.mapreduce.TestCrossAPICounters

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2897//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2897//console

This message is automatically generated.
                
> Inconsistency in reduce input record counters between the stable and evolving APIs
> ----------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4694
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4694
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.0.0-alpha
>            Reporter: Harsh J
>            Assignee: Harsh J
>              Labels: inconsistency, regression, test
>         Attachments: MAPREDUCE-4694.patch, MAPREDUCE-4694.patch
>
>
> In the stable (mapred) API execution, if the values iterator is skipped by a user, the
records underneath it aren't counted in the "Reduce input records" counter as the key progresses
to the next unique one. In the evolving API (mapreduce) API execution, if the values iterator
is skipped by a user, the records underneath it is still counted as the key progresses to
the next unique one.
> This behavior comes to me as a faulty one in the old API. A "Reduce input records" counter
must always define all the records that have been passed into a reducer (cause they are read
regardless of skipping), and both API's record counting despite user applications must be
consistent.
> I'll post a test case illustrating this shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message