MultipleOutputs in new API creates needless TaskAttemptContexts
---------------------------------------------------------------
Key: MAPREDUCE-2740
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2740
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Todd Lipcon
Fix For: 0.23.0
MultipleOutputs.write creates a new TaskAttemptContext, which we've seen to
take a significant amount of CPU. The TaskAttemptContext constructor creates a
JobConf, gets current UGI, etc. I don't see any reason it needs to do this,
instead of just creating a single TaskAttemptContext when the InputFormat is
created (or lazily but cached as a member)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira