You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-dev@hadoop.apache.org by "Chuan Liu (JIRA)" <ji...@apache.org> on 2013/12/07 02:49:35 UTC

[jira] [Created] (MAPREDUCE-5674) Missing start and finish time in mapred.JobStatus

Chuan Liu created MAPREDUCE-5674:
------------------------------------

             Summary: Missing start and finish time in mapred.JobStatus
                 Key: MAPREDUCE-5674
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5674
             Project: Hadoop Map/Reduce
          Issue Type: Bug
    Affects Versions: 3.0.0
            Reporter: Chuan Liu
            Assignee: Chuan Liu


The JobStatus obtained from the JobClient or runningJob has no start or finish time for the job -- the start and finish time is always 0. This is a regression with respect to 1.0 mapreduce client and JobStatus API. This can also lead to regressions in downstream projects. For example, we discovered the problem in webhcat that the jobstatus for mapreduce job submmited to webhcat always reports start time as 0.



--
This message was sent by Atlassian JIRA
(v6.1#6144)