[
https://issues.apache.org/jira/browse/MAPREDUCE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated MAPREDUCE-434:
--------------------------------
Attachment: MAPREDUCE-434.patch
I ran the MapReduce tests and they all passed except
TestMRKeyFieldBasedComparator. The problem was that it uses LJR with 2
reducers. However, when the LJR runs it used to (before this change) silently
change the number of reducers to 1. With this change it was using 2 reducers
which caused a failure since it was expecting the first output to be a
particular partition.
I changed the test to use a single reducer (which it has been doing all along
due to the previous behaviour of LJR). This should be ready to be committed now.
> local map-reduce job limited to single reducer
> ----------------------------------------------
>
> Key: MAPREDUCE-434
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-434
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Environment: local job tracker
> Reporter: Yoram Arnon
> Assignee: Aaron Kimball
> Priority: Minor
> Attachments: MAPREDUCE-434.2.patch, MAPREDUCE-434.3.patch,
> MAPREDUCE-434.4.patch, MAPREDUCE-434.5.patch, MAPREDUCE-434.6.patch,
> MAPREDUCE-434.patch, MAPREDUCE-434.patch, MAPREDUCE-434.patch
>
>
> when mapred.job.tracker is set to 'local', my setNumReduceTasks call is
> ignored, and the number of reduce tasks is set at 1.
> This prevents me from locally debugging my partition function, which tries to
> partition based on the number of reduce tasks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira