You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2013/05/15 00:57:15 UTC

[jira] [Updated] (MAPREDUCE-5235) mapred.Counters incompatiblity issues with MR1

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

Zhijie Shen updated MAPREDUCE-5235:
-----------------------------------

    Summary: mapred.Counters incompatiblity issues with MR1  (was: MAX_GROUP_LIMIT is removed from Counters in mapred)
    
> 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
>
> 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