[
https://issues.apache.org/jira/browse/HADOOP-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549356
]
Hadoop QA commented on HADOOP-2376:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12371207/sort-no-maps.patch
against trunk revision r602002.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1292/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1292/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1292/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1292/console
This message is automatically generated.
> 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.
