[
https://issues.apache.org/jira/browse/MAPREDUCE-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246743#comment-14246743
]
Hudson commented on MAPREDUCE-6194:
-----------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1993 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1993/])
MAPREDUCE-6194. Bubble up final exception in failures during creation of output
collectors. Contributed by Varun Saxena. (harsh: rev
298d09c9b583088f364038adcb1edf1eb1c2c196)
* hadoop-mapreduce-project/CHANGES.txt
*
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java
> Bubble up final exception in failures during creation of output collectors
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-6194
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6194
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
> Affects Versions: 2.6.0
> Reporter: Harsh J
> Assignee: Varun Saxena
> Priority: Minor
> Labels: newbie
> Fix For: 2.7.0
>
> Attachments: MAPREDUCE-6194.patch
>
>
> MAPREDUCE-5974 added in ability to instantiate multiple OCs, but if none of
> them are able to load it "throws" only a final a generic message: {{"Unable
> to initialize any output collector"}}
> The older behaviour was to throw the actual instantiation exception back, so
> it makes it to client logs with an actual meaningful error.
> Now the clients need to go take a look at the task's logs to find the WARNs
> that represent the failure in instantiation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
