[
https://issues.apache.org/jira/browse/HADOOP-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530501
]
Doug Cutting commented on HADOOP-1873:
--------------------------------------
> void setWritable(String key, Writable value) throws IOException;
Yikes. I guess we can go that way, but it's going to encourage putting big
binary stuff into XML, which is not optimal.
> Obviously the current usage doesn't work at all once we have permissions.
That's not clear to me. Can't we make the system directory world-writable but
readable only by the jobtracker/tasktracker user?
> give the JobTracker super-user dfs permissions
I hope we don't have to do that. We should have a user id for the job
submitter and a user id for the jobtracker/tasktracker. For a dynamic,
single-user mapred cluster, these could be the same. For a static mapred
cluster, these could be different. In either case, other users should not be
able to read one's job files.
> 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: Raghu Angadi
>
> 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.
