-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12687152/MAPREDUCE-6194.patch
against trunk revision 25a0440.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 javadoc. There were no new javadoc warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to introduce 13 new Findbugs (version 2.0.3) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5079//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5079//artifact/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5079//console
This message is automatically generated.
If someone would like to try working on this, the file to edit is hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java, and essentially we'd want some variable storing the last WARNed exception and rethrowing that at the end with a wrapped message such as "Final error in constructing the collector was:".
A more clever impl. could include messages from each of the attempt exceptions, collecting them all, but the above would usually do for most of users only using the standard single/pair of collectors.