hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4878) JobID.forName() isn't strict enough
Date Fri, 14 Dec 2012 00:46:12 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531863#comment-13531863

Alejandro Abdelnur commented on MAPREDUCE-4878:

This could be considered a backward incompat change. I'd like somebody else opinion before
committing it.
> 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
>             Fix For: 1.2.0, 2.0.3-alpha
>         Attachments: HADOOP-9065_branch-1.patch, HADOOP-9065.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message