hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1873) User permissions for Map/Reduce
Date Wed, 28 Nov 2007 19:53:43 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546365

Doug Cutting commented on HADOOP-1873:

> Setting job files to be worldwide readable but owner-writable;

Will we permit per-file permissions?  Wasn't there some discussion that we should only support
per-directory permissions?

There are two entities which must be able to read job files: the jobtracker/tasktracker and
the submitter.  It seems to me this can be handled by setting the group to be the jobtracker/tasktracker
group, and the owner to be the submitter.  Then they should be readable by user and group
but not world.  The group of jobtracker/tasktracker could perhaps be returned by a JobClient

> User permissions for Map/Reduce
> -------------------------------
>                 Key: HADOOP-1873
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1873
>             Project: Hadoop
>          Issue Type: Improvement
>            Reporter: Raghu Angadi
>            Assignee: Hairong Kuang
> HADOOP-1298 and HADOOP-1701 add permissions and pluggable security for DFS files and
DFS accesses. Same users permission should work for Map/Reduce jobs as well. 
> User persmission should propegate from client to map/reduce tasks and all the file operations
should be subject to user permissions. This is transparent to the user (i.e. no changes to
user code should be required). 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message