[
https://issues.apache.org/jira/browse/MAPREDUCE-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830688#action_12830688
]
Devaraj Das commented on MAPREDUCE-1307:
----------------------------------------
The advantage with the file-system model is that it is really simple and would
handle almost all cases that we might come across. The ACL model is also fine
though it is tedious to specify that and pass it to the JobTracker. But it is
good to look at the long term... So in that sense, I am tending to agree with
Hemanth/Vinod.
W.r.t condor, torque, i don't think that they have job level read/write
permissions model. They are more concerned with the queue operations. But it is
something that could be checked.
> Introduce the concept of Job Permissions
> ----------------------------------------
>
> Key: MAPREDUCE-1307
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1307
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: security
> Reporter: Devaraj Das
> Fix For: 0.22.0
>
> Attachments: 1307-early-1.patch
>
>
> It would be good to define the notion of job permissions analogous to file
> permissions. Then the JobTracker can restrict who can "read" (e.g. look at
> the job page) or "modify" (e.g. kill) jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
