[
https://issues.apache.org/jira/browse/HADOOP-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624270#action_12624270
]
Owen O'Malley commented on HADOOP-3698:
---------------------------------------
I'd prefer just using hadoop-site.xml for the generic properties.
I'd suggest renaming the ResourceManagerConf to something like QueueManager and
merging in QueueAccessVerifier. It would look something like:
{code}
class QueueManager {
QueueManager(Configuration conf) { ... }
List<String> getQueueNames() { ... }
static enum QueueOperation { SUBMIT_JOB, ADMINISTER_JOBS }
boolean hasAccess(String queueName, UserGroupInformation user, QueueOperation
action) { ... }
}
{code}
> Implement access control for submitting jobs to queues in the JobTracker
> ------------------------------------------------------------------------
>
> Key: HADOOP-3698
> URL: https://issues.apache.org/jira/browse/HADOOP-3698
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Fix For: 0.19.0
>
>
> HADOOP-3445 implements multiple queues in the JobTracker as part of the new
> resource manager for Hadoop (HADOOP-3421). There needs to be a mechanism to
> control who can submit jobs to a specified queue. This JIRA is for tracking
> the requirements, approach and implementation for the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
