hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mayank Bansal (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MAPREDUCE-5235) MAX_GROUP_LIMIT is removed from Counters in mapred
Date Tue, 14 May 2013 18:03:18 GMT

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

Mayank Bansal reassigned MAPREDUCE-5235:
----------------------------------------

    Assignee: Mayank Bansal  (was: Zhijie Shen)
    
> MAX_GROUP_LIMIT is removed from Counters in mapred
> --------------------------------------------------
>
>                 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

Mime
View raw message