[
https://issues.apache.org/jira/browse/HADOOP-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624073#action_12624073
]
Sanjay Radia commented on HADOOP-3698:
--------------------------------------
Hemant says:
>In the same discussions, it seemed like sysadmins would like to control this
>themselves as well. Again, there did not seem a need to set up access control.
What do you mean by sysadmins? - do they have special priviledges beyond the
ACL. I think it makes sense
for the superuser and the supergroup (of HDFS) to have full permissions to job
queues without the need for their username/groupname appear in the ACL. Is
that what you meant by sysadmins?
>That said, it is really simple to add new operations in the design above when
>we feel we need it. That's one advantage with this approach.
I suggest we add the "changeACL operation right now; its default list should be
null (ie only the superuser/supergroup can modify it).
> 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.
