hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4355) Add startTime to RunningJob
Date Wed, 27 Jun 2012 03:39:44 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401941#comment-13401941

Alejandro Abdelnur commented on MAPREDUCE-4355:

I'll revert the current commit WED morning. 

I think adding a getJobStatus() method to RunningJob would be more comprehensive that just
adding startTime(). Arun, would you agree with that?
> Add startTime to RunningJob
> ---------------------------
>                 Key: MAPREDUCE-4355
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4355
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: mrv1, mrv2
>    Affects Versions: 1.0.3, 2.0.0-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>             Fix For: 1.1.0, 2.0.1-alpha
>         Attachments: MR-4355_mr1.patch, MR-4355_mr2.patch
> To read the start-time of a particular job, one should not need to getAllJobs() and iterate
through them.
> getJob(JobID) returns RunningJob, which doesn't hold the job's start time.
> Hence, we need to either add getJobStatus(JobID) to the API or add startTime to RunningJob.
Doing the latter.

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


View raw message