[
https://issues.apache.org/jira/browse/MAPREDUCE-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913575#comment-13913575
]
Karthik Kambatla commented on MAPREDUCE-4878:
---------------------------------------------
This should be okay.
In theory, we are changing the behavior, but it is only to correct previously
incorrect behavior -
http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html#Semantic_compatibility
> JobID.forName() isn't strict enough
> -----------------------------------
>
> Key: MAPREDUCE-4878
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4878
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: HADOOP-9065.patch, HADOOP-9065_branch-1.patch
>
>
> If you have a job running as job_201208221603_0003, and then try to kill a
> job passing id job_201208221603_003, it will kill job_201208221603_0003
> because the last part of the JobID is parsed as an integer. We should make
> JobID.forName() stricter to prevent this and similar situations as the
> current behavior isn't so obvious.
> More specifically, we shouldn't accept JobIDs if the last part of the JobID
> is:
> {{-}} less than 4 characters (e.g. _003, _123)
> {{-}} more than 4 characters and has a leading zero (e.g. _00003, _01234)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
