[
https://issues.apache.org/jira/browse/HADOOP-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-5020:
-------------------------------
Attachment: HADOOP-5020-v1.0.patch
Attaching a simple straightforward fix that addresses the issue. Instead of
creating a new JobStatus object, setting the relevant fields of the old status.
Result of _test-patch_
{noformat}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 6 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
{noformat}
> JobStatus of killed JobInProgress does not carry forward start time of the Job
> ------------------------------------------------------------------------------
>
> Key: HADOOP-5020
> URL: https://issues.apache.org/jira/browse/HADOOP-5020
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Sreekanth Ramakrishnan
> Attachments: HADOOP-5020-v1.0.patch
>
>
> If an initialized job is killed, the jobs start time is set to zero.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
