hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Subramaniam Krishnan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3924) Add a 'Killed' job status
Date Fri, 19 Sep 2008 08:14:44 GMT

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

Subramaniam Krishnan updated HADOOP-3924:

    Hadoop Flags:   (was: [Reviewed])
          Status: Patch Available  (was: Open)

Updated with Arun's & Sharad's comments..thanks.

Not updating JobStatus to enum right now as it affects too many files, have raised a separate
JIRA ([Hadoop-4214]) for the same.

> 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
>            Assignee: Subramaniam Krishnan
>            Priority: Critical
>         Attachments: patch-3924_v1.txt, patch-3924_v2.txt, patch-3924_v3.txt, patch-3924_v4.txt,
patch-3924_v5.txt, patch-3924_v6.txt, patch-3924_v7.txt
> 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