You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Vinod K V (JIRA)" <ji...@apache.org> on 2010/01/25 07:34:38 UTC

[jira] Commented: (MAPREDUCE-1307) Introduce the concept of Job Permissions

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804407#action_12804407 ] 

Vinod K V commented on MAPREDUCE-1307:
--------------------------------------

Why have a separate setup of access control besides the one that JT already inherits from its own filesystem? This I mention, because elsewhere (MAPREDUCE-744), we used the JT filesystem's user/group permissions to see if jobs of multiple users can share localization of distributed-cache files (on the TTs). Definitely, these two should be reconciled, no?

> 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.