hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5235) mapred.Counters incompatiblity issues with MR1
Date Wed, 22 May 2013 13:03:27 GMT

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

Hudson commented on MAPREDUCE-5235:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk #1406 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1406/])
    MAPREDUCE-5235. Bring back old fields and exceptions in Counters for binary compatibility
with mapred in 1.x. Contributed by Mayank Bansal (Revision 1484992)

     Result = FAILURE
vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1484992
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/Counters.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/counters/LimitExceededException.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapred/TestCounters.java

                
> mapred.Counters incompatiblity issues with MR1
> ----------------------------------------------
>
>                 Key: MAPREDUCE-5235
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5235
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Mayank Bansal
>             Fix For: 2.0.5-beta
>
>         Attachments: MAPREDUCE-5235-trunk-1.patch, MAPREDUCE-5235-trunk-2.patch, MAPREDUCE-5235-trunk-3.patch
>
>
> MAX_GROUP_LIMIT is removed from Counters in mapred in MR2. Though it seems not to be
the variable that will be referred by the user code. It was actually configurable value MR1.
We should investigate why the upper bound doesn't need to be checked in MR2.

--
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