Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 81560 invoked from network); 2 Apr 2009 17:56:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Apr 2009 17:56:34 -0000 Received: (qmail 21425 invoked by uid 500); 2 Apr 2009 17:56:34 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 21369 invoked by uid 500); 2 Apr 2009 17:56:33 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 21359 invoked by uid 99); 2 Apr 2009 17:56:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 17:56:33 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 17:56:33 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0AC77234C055 for ; Thu, 2 Apr 2009 10:56:13 -0700 (PDT) Message-ID: <680266171.1238694973043.JavaMail.jira@brutus> Date: Thu, 2 Apr 2009 10:56:13 -0700 (PDT) From: "rahul k singh (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-5419) Provide a way for users to find out what operations they can do on which M/R queues In-Reply-To: <802526595.1236316556329.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rahul k singh updated HADOOP-5419: ---------------------------------- Attachment: hadoop-5419.patch uploaded the latest patch with suggestions after discussion with hemanth. In addition mentioning some points about the fix , which weren't very clear from my update above. -Added new API in JobSubmissionProtocol getQueueAclsInfo.it takes username and returns QueueAclsInfo class -Created new QueueAclsInfo class , it is a Writable class. -QueueManager implements the method and synchronized. The method is synchronized because aclsMap in QueueManger might get (incase of automatic acls refresh feature)refreshed.This if happens will lead to issues. -In JobClient we are doing {code} ugi = UnixUserGroupInformation.login(job, true); UnixUserGroupInformation.setCurrentUser(ugi);{code} This is done so that we get ugi value in JobQueueClient which displaying the acls info , as we are displaying username. Anythoughts? -We had discussed about the web ui part , we thought that any user seeing other acls might lead to some issues. If at all we allow this we need to define special kind of user permissions (for example : administrator) so that those users can view the acls of all the users. > Provide a way for users to find out what operations they can do on which M/R queues > ----------------------------------------------------------------------------------- > > Key: HADOOP-5419 > URL: https://issues.apache.org/jira/browse/HADOOP-5419 > Project: Hadoop Core > Issue Type: Improvement > Components: mapred > Reporter: Hemanth Yamijala > Assignee: rahul k singh > Attachments: hadoop-5419.patch, hadoop-5419.patch, hadoop-5419.patch > > > This issue is to provide an improvement on the existing M/R framework to let users know which queues they have access to, and for what operations. One use case for this would that currently there is no easy way to know if the user has access to submit jobs to a queue, until it fails with an access control exception. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.