You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/05/03 15:17:03 UTC

[jira] [Commented] (MAPREDUCE-2457) job submission should inject group.name (on the JT side)

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

Hudson commented on MAPREDUCE-2457:
-----------------------------------

Integrated in Hadoop-Mapreduce-22-branch #44 (See [https://builds.apache.org/hudson/job/Hadoop-Mapreduce-22-branch/44/])
    MAPREDUCE-2457. Job submission should inject group.name on the JobTracker. Contributed by Alejandro Abdelnur.


> job submission should inject group.name (on the JT side)
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-2457
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2457
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.21.0, 0.22.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>            Priority: Critical
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-2457-1.patch, MAPREDUCE-2457.patch
>
>
> Until Hadoop 0.20, the JobClient was injecting the property 'group.name' on the JobConf submitted to the JobTracker.
> Since Hadoop 0.21, due to security related changes, this is not done anymore.
> This breaks backwards compatibility for jobs/components that expect the 'group.name' to be automatically set at submission time.
> An example of a component being affected by this change is the FairScheduler where it is common to use the group.name as pool name. Different from other properties, a special characteristic of the group.name is that its value cannot be tampered by a user.
> For security reasons this should not be done (as it was done before) in the JobClient side. Instead, it should be done in the JobTracker when the JobConf is received.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira