[
https://issues.apache.org/jira/browse/MAPREDUCE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767673#action_12767673
]
Jothi Padmanabhan commented on MAPREDUCE-947:
---------------------------------------------
bq. o.a.h.mapreduce.OutputCommitter.abortJob calls commitJob by default,
shouldn't it call cleanupJob instead?
I am not sure if we want to do this. The user could implement commitJob and not
a cleanupJob, in which case abortJob should call commitJob by default, no?
> OutputCommitter should have an abortJob method
> ----------------------------------------------
>
> Key: MAPREDUCE-947
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-947
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.21.0
> Reporter: Owen O'Malley
> Assignee: Amar Kamat
> Fix For: 0.22.0
>
> Attachments: mapred-948-v1.12-branch-0.20-internal.patch,
> mapred-948-v1.12.patch, mapred-948-v1.13-branch-0.20-internal.patch,
> mapred-948-v1.2.patch, mapred-948-v1.3.patch, mapred-948-v1.4.patch,
> mapred-948-v1.7.patch, mapred-948-v2.1-branch-0.20.patch,
> mapred-948-v2.3-branch-0.20.patch, mapred-948-v2.3.patch,
> mapred-948-v3.1.patch, mapred-948-v3.2.patch, mapred-948-v3.4.patch,
> mr-947-trunk.patch
>
>
> The OutputCommitter needs an abortJob method to clean up from failed jobs.
> Currently there is no way to distinguish between failed or succeeded jobs,
> making it impossible to write output promotion code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
