[
https://issues.apache.org/jira/browse/MAPREDUCE-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281539#comment-13281539
]
Subroto Sanyal commented on MAPREDUCE-4280:
-------------------------------------------
{quote}
This is fixed in MR2's LocalJobRunner in 2.x and trunk via MAPREDUCE-3563. We
probably have to backport it to 1.x.
{quote}
I feel even this fix doesn't honors the cleanupJob of CustomCommitter. Seems
needs to be fixed in some 2.x as well.
> LocalJobRunner doesn't honor custom OutputCommiter cleanupJob
> -------------------------------------------------------------
>
> Key: MAPREDUCE-4280
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4280
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Subroto Sanyal
>
> I have an implementation SampleFileOutputCommiter which extends
> org.apache.hadoop.mapred.FileOutputCommitter . The implementation has
> specific code to be executed during cleanupJob() execution.
> When the framework(LocalJobRunner) makes a call to commitJob(), the framework
> never takes care of calling the cleanupJob() instead it calls
> org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter commitJob() which
> internally calls its own cleanupJob().
> Though the method cleanupJob is deprecated but, still I feel the framework
> should take care of executing it as it is being executed from
> org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter.
> Currently the framework is not letting the Jobs written with MRV1 to run
> properly.
--
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
