[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ravi Gummadi updated MAPREDUCE-1542:
------------------------------------

    Attachment: 1542.20S.1.patch

> So, why can't the mrowner and acls be created inside this class when it is 
> instantiated ? Then, isMROwnerOrAdmin can be implemented directly in 
> JobACLsManager itself.

Moved adminsACL and the method isMROwnerOrAdmin() to JobACLsManager. Since 
mrOwner is used in JobTracker and TaskTracker at few other places, keeping 
mrOwner as part of JobTracker and TaskTracker objects instead of moving to 
JobACLsManager.

Attaching patch for earlier version of hadoop with review comments 
incorporated. Not for commit here.

> Deprecate mapred.permissions.supergroup in favor of 
> hadoop.cluster.administrators
> ---------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1542
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1542
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: security
>            Reporter: Vinod K V
>            Assignee: Ravi Gummadi
>             Fix For: 0.22.0
>
>         Attachments: 1542.20S.1.patch, 1542.20S.patch, 1542.patch, 
> 1542.v1.patch, mapreduce-1542-y20s.patch
>
>
> HADOOP-6568 added the configuration {{hadoop.cluster.administrators}} through 
> which admins can configure who the superusers/supergroups for the cluster 
> are. MAPREDUCE itself already has {{mapred.permissions.supergroup}} (which is 
> just a single group). As agreed upon at HADOOP-6568, this should be 
> deprecated in favor of {{hadoop.cluster.administrators}}.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to