Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1715452180.1238661973509.JavaMail.jira@brutus>
Date: Thu, 2 Apr 2009 01:46:13 -0700 (PDT)
From: "rahul k singh (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Issue Comment Edited: (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


    [ https://issues.apache.org/jira/browse/HADOOP-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694916#action_12694916 ] 

rahul k singh edited comment on HADOOP-5419 at 4/2/09 1:45 AM:
---------------------------------------------------------------

to answer nigel comments:
bq.  This should be available thru cmd line and web ui. 
As of now there is no way of authentication for user on web ui . So we cannot show per user data. 
Moreover showing acls for all the user's ,imho, might not be such a good thing.

      was (Author: rksingh):
    to answer nigel comments:
"bq. " This should be available thru cmd line and web ui. 
As of now there is no way of authentication for user on web ui . So we cannot show per user data. 
Moreover showing acls for all the user's ,imho, might not be such a good thing.
  
> 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
>
>
> 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.