hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-947) OutputCommitter should have an abortJob method
Date Wed, 07 Oct 2009 08:08:31 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amar Kamat updated MAPREDUCE-947:
---------------------------------

    Attachment: mapred-948-v1.7.patch

Attaching a new patch that adds a new method _abortJob(JobContext context, boolean failed)_
to OutputCommitter. Adding _failed for failed jobs and __killed_ for killed jobs in FileOutputCommitter.
_test-patch_ passed on my box. Running ant tests.

> 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
>            Reporter: Owen O'Malley
>            Assignee: Amar Kamat
>             Fix For: 0.21.0
>
>         Attachments: mapred-948-v1.2.patch, mapred-948-v1.3.patch, mapred-948-v1.4.patch,
mapred-948-v1.7.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.


Mime
View raw message