hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5235) mapred.Counters incompatiblity issues with MR1
Date Thu, 16 May 2013 02:09:16 GMT

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

Zhijie Shen commented on MAPREDUCE-5235:

Should you add tests in mapred.TestCounters? mapreduce.TestCounters is for mapreduce.Counters.

--- hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/TestCounters.java
+++ hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/TestCounters.java

Not sure why functions with the same input need to be called three times. The inner functions
should be deterministic, right?

for (int i = 0; i < 3; ++i) {

> 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
>         Attachments: MAPREDUCE-5235-trunk-1.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

View raw message