[ https://issues.apache.org/jira/browse/MAPREDUCE-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096575#comment-14096575 ]
Todd Lipcon commented on MAPREDUCE-5974: ---------------------------------------- Hey Chris. So, is that a +0? Should I go ahead and commit this to the native task branch? > Allow map output collector fallback > ----------------------------------- > > Key: MAPREDUCE-5974 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5974 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: task > Affects Versions: 2.6.0 > Reporter: Todd Lipcon > Assignee: Todd Lipcon > Attachments: mapreduce-5974.txt > > > Currently we only allow specifying a single MapOutputCollector implementation > class in a job. It would be nice to allow a comma-separated list of classes: > we should try each collector implementation in the user-specified order until > we find one that can be successfully instantiated and initted. > This is useful for cases where a particular optimized collector > implementation cannot operate on all key/value types, or requires native > code. The cluster administrator can configure the cluster to try to use the > optimized collector and fall back to the default collector. -- This message was sent by Atlassian JIRA (v6.2#6252)