[
https://issues.apache.org/jira/browse/MAPREDUCE-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated MAPREDUCE-5674:
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
3.0.0
Status: Resolved (was: Patch Available)
I committed this to trunk, branch-2 and branch-2.3. Chuan, thank you for
providing this fix.
> 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
> Components: client
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Chuan Liu
> Assignee: Chuan Liu
> Fix For: 3.0.0, 2.3.0
>
> Attachments: MAPREDUCE-5674.2.patch, MAPREDUCE-5674.patch
>
>
> 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.4#6159)
