Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 96B16910A for ; Mon, 27 Feb 2012 22:06:12 +0000 (UTC) Received: (qmail 93370 invoked by uid 500); 27 Feb 2012 22:06:12 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 93275 invoked by uid 500); 27 Feb 2012 22:06:12 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 93258 invoked by uid 99); 27 Feb 2012 22:06:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 22:06:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Feb 2012 22:06:09 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id EE77B33D12F for ; Mon, 27 Feb 2012 22:05:48 +0000 (UTC) Date: Mon, 27 Feb 2012 22:05:48 +0000 (UTC) From: "John George (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1184717503.25098.1330380348978.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <6849733.25003.1330379755532.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-3929) output of mapred -showacl is not clear 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/MAPREDUCE-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217622#comment-13217622 ] John George commented on MAPREDUCE-3929: ---------------------------------------- The following are the inconsistencies or confusing output that I see. 1. If the parent queue specifically defines a value in capacity-scheduler.xml, it shows up in its permitted operation and any of the children derived from it. If a parent queue derives this value (from its forefathers) this value will not be shown. 2. root even though is a parent queue, will show the operation it is allowed even if it is by omission, but none of the other parent queues show that. Here is the output of a mapred -showacl command: Queue Operations ===================== root ADMINISTER_QUEUE,SUBMIT_APPLICATIONS a SUBMIT_APPLICATIONS a1 ADMINISTER_QUEUE,SUBMIT_APPLICATIONS a2 ADMINISTER_QUEUE,SUBMIT_APPLICATIONS b ADMINISTER_QUEUE,SUBMIT_APPLICATIONS c c1 ADMINISTER_QUEUE,SUBMIT_APPLICATIONS c2 ADMINISTER_QUEUE,SUBMIT_APPLICATIONS d ADMINISTER_QUEUE,SUBMIT_APPLICATIONS Here, the root queue shows that it is allowed both AQ, and SA operations, but parent queue 'a' and 'c' do not list AQ. The reason parent queue 'a' lists SA is because it was specifically mentioned in the config. To me, it seems like either the parent queues should show all the operations it's child queues are allowed or not show anything. Making it such that the operations specifically listed in config will only be shown while the other operations (even though are allowed) wont be shown is confusing to the users. > output of mapred -showacl is not clear > -------------------------------------- > > Key: MAPREDUCE-3929 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3929 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.24.0, 0.23.2, 0.23.3 > Reporter: John George > Assignee: John George > > output of 'mapred queue -showacls' is not very clear. This JIRA is aimed at either fixing that or adding something to the document to make it clear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira