[
https://issues.apache.org/jira/browse/HADOOP-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623830#action_12623830
]
Tsz Wo (Nicholas), SZE commented on HADOOP-3698:
------------------------------------------------
- It seems to me that job operations and file system operations are similar:
|job|file|
|submit/delete job|create/delete file|
|set job attributes|set file attributes|
|queue|directory|
|list queue| list directory|
|create/delete queue|create/delete directory|
Is the analogue right? If yes, we might want to have a similar access control
model as the one in file system.
- I think ADMINISTER_JOBS sounds too general. We might want to divide it into
more specific operations, say DELETE_JOB, SET_JOB_PRIORITY, etc.
> 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.
