[
https://issues.apache.org/jira/browse/HADOOP-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556969#action_12556969
]
Doug Cutting commented on HADOOP-1873:
--------------------------------------
Another option: In the FileSystem.create and FileSystem.mkdirs static utility
methods, we might create the file or directory first, then set the protection.
This has the disadvantage of making two RPC calls, but it has the advantage of
being thread safe. In the current case (job submission) the performance impact
of these extra RPCs would be negligible, no?
> 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
> Attachments: mapred.patch, mapred2.patch, mapred3.patch,
> mapred4.patch, mapred5.patch, mapred6.patch
>
>
> 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.
