You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/12/07 08:49:43 UTC
[jira] Updated: (HADOOP-2376) The sort example shouldn't override
the number of maps
[ https://issues.apache.org/jira/browse/HADOOP-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated HADOOP-2376:
----------------------------------
Attachment: sort-no-maps.patch
This just pulls out the code from the example that is trying to pick a good number of maps. Letting it match the number of input blocks is a much better idea.
> The sort example shouldn't override the number of maps
> ------------------------------------------------------
>
> Key: HADOOP-2376
> URL: https://issues.apache.org/jira/browse/HADOOP-2376
> Project: Hadoop
> Issue Type: Bug
> Components: examples
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Fix For: 0.16.0
>
> Attachments: sort-no-maps.patch
>
>
> The sort example currently overrides the number of maps. It should just take the default, because the current behavior can end up with a bad number of maps by default. In particular, I had a small data set where the sort picked too many maps and split blocks badly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.