Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <31736150.243851268476107243.JavaMail.jira@brutus.apache.org>
Date: Sat, 13 Mar 2010 10:28:27 +0000 (UTC)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1542) Deprecate
 mapred.permissions.supergroup in favor of hadoop.cluster.administrators
In-Reply-To: <826514864.26241267415947384.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hemanth Yamijala commented on MAPREDUCE-1542:
---------------------------------------------

I looked again at TestWebUIAuthorization. It does look like it is covering everything required. Can you confirm if my understanding on this test case is right:

Basically, we have configured adminGroup as the admin ACL. 'admin' user is part of the adminGroup (as defined in the custom user to group mapping). Then we drive all operations setting 'admin' as the user. All of these will cover the code path of checking the adminUser because these will be mapped to the adminGroup which is in the administrators ACL. Correct ?

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