You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2014/07/17 18:17:09 UTC

[jira] [Created] (MAPREDUCE-5974) Allow map output collector fallback

Todd Lipcon created MAPREDUCE-5974:
--------------------------------------

             Summary: 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


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)