[ https://issues.apache.org/jira/browse/MAPREDUCE-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149646#comment-13149646 ]
Bhallamudi Venkata Siva Kamesh commented on MAPREDUCE-2493: ----------------------------------------------------------- When we use new API, the OutputCommitter associated with the FileOutputFormat is FileOutputCommitter. Where as for the old API, OutputCommitter is reading from the conf object. {code} if (useNewApi) { if (LOG.isDebugEnabled()) { LOG.debug("using new api for output committer"); } outputFormat = ReflectionUtils.newInstance(taskContext.getOutputFormatClass(), job); committer = outputFormat.getOutputCommitter(taskContext); } else { committer = conf.getOutputCommitter(); } {code} > New Api FileOutputFormat does not honour user specified OutputCommitter > ----------------------------------------------------------------------- > > Key: MAPREDUCE-2493 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2493 > Project: Hadoop Map/Reduce > Issue Type: Bug > Reporter: Sharad Agarwal > > o.a.h.mapreduce.lib.output.FileOutputFormat always uses the default > FileOutputCommitter. It ignores the user specified OutputCommitter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira