hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rahul k singh (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-861) Modify queue configuration format and parsing to support a hierarchy of queues.
Date Mon, 07 Sep 2009 06:32:57 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

rahul k singh updated MAPREDUCE-861:

    Attachment: MAPREDUCE-861-4.patch

Incorporated all the comments except 

1.In DeprecatedHierarchyBuilder we are still not checking if ACLs are disabled before parsing
them. Note though that this is being done for the QueueHierarchyBuilder.
Lots of testcases esp. in TestQueueManager are written with an assumption that Map<String,
AccessControlList> list is created for the Queue object all the time.
esp in case of setting "mapred.acls.enabled" = true using conf.set . There are lots of NullPointerException
if we dont generate this empty object. Hence not accommodating this comment , as it is a significant
change in testcase and moreover for deprecated stuff and having this does empty Map<String,AccessControlList>
doesn't effect the overall behaviour at all.

> Modify queue configuration format and parsing to support a hierarchy of queues.
> -------------------------------------------------------------------------------
>                 Key: MAPREDUCE-861
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-861
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>            Reporter: Hemanth Yamijala
>            Assignee: rahul k singh
>         Attachments: MAPREDUCE-861-1.patch, MAPREDUCE-861-2.patch, MAPREDUCE-861-3.patch,
> MAPREDUCE-853 proposes to introduce a hierarchy of queues into the Map/Reduce framework.
This JIRA is for defining changes to the configuration related to queues. 
> The current format for defining a queue and its properties is as follows: mapred.queue.<queue-name>.<property-name>.
For e.g. mapred.queue.<queue-name>.acl-submit-job. The reason for using this verbose
format was to be able to reuse the Configuration parser in Hadoop. However, administrators
currently using the queue configuration have already indicated a very strong desire for a
more manageable format. Since, this becomes more unwieldy with hierarchical queues, the time
may be good to introduce a new format for representing queue configuration.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message