hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3924) Add a 'Killed' job status
Date Fri, 08 Aug 2008 05:03:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620838#action_12620838

Alejandro Abdelnur commented on HADOOP-3924:

{{JobStatus}} should have a KILLED status.

{{RunnningJob}} should expose either the {{JobStatus}} or a new method {{isKilled}}

Maybe making {{JobStatus}} and enum and exposing that via the {{RunningJob}} would be a more
elegant solution.

> Add a 'Killed' job status
> -------------------------
>                 Key: HADOOP-3924
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3924
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: mapred
>         Environment: all
>            Reporter: Alejandro Abdelnur
>            Priority: Critical
> It is not possible, via APIs, to know if a job has been killed, only that has not been

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message