[
https://issues.apache.org/jira/browse/HADOOP-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-4420:
------------------------------
Resolution: Fixed
Fix Version/s: 0.20.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I've just committed this. Thanks Aaron!
See HADOOP-4725 for a follow-on feature to notify clients when they pass bad
job IDs.
> JobTracker.killJob() doesn't check for the JobID being valid
> ------------------------------------------------------------
>
> Key: HADOOP-4420
> URL: https://issues.apache.org/jira/browse/HADOOP-4420
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.18.0, 0.18.1, 0.18.2
> Reporter: Steve Loughran
> Assignee: Aaron Kimball
> Priority: Minor
> Fix For: 0.19.1, 0.20.0
>
> Attachments: hadoop-4420.patch, hadoop-4420.patch.2
>
>
> As with HADOOP-4419, JobTracker.killJob() assumes that the supplied JobID
> always matches to a valid job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
