hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Gummadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1542) Deprecate mapred.permissions.supergroup in favor of hadoop.cluster.administrators
Date Thu, 04 Mar 2010 06:00:28 GMT

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

Ravi Gummadi commented on MAPREDUCE-1542:
-----------------------------------------

Removing mapred.permissions.supergroup and the recently renamed mapreduce.jobtracker.permissions.supergroup
in favour of the config hadoop.cluster.administrators that can take sequence of users followed
by sequence of groups.

As mapred.permissions.supergroup is not documented anywhere and as maintaining compatibility
between mapred.permissions.supergroup and hadoop.cluster.administrators seems to be very difficult(would
need lot of hacking in the code as the values for these 2 keys are different and in different
formats), the old config will not be supported with this patch.

> 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
>
>
> 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.


Mime
View raw message