[
https://issues.apache.org/jira/browse/HADOOP-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555729#action_12555729
]
Doug Cutting commented on HADOOP-1873:
--------------------------------------
It's unfortunate that we have to alter the configuration to set the protections
we want.
To make this safer, we could either:
- restore the umask in a 'finally' clause, so it's restored on exceptions; or
- set the umask in a copy of the configuration, so that it doesn't need to be
restored.
In either case, it might be cleaner to have utility methods that perform file
create and mkdir with a modified umask.
Also, in JobClient, the umask is restored after the job is serialized, so the
jobtracker will see the modified value, not the original.
> 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
>
>
> 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.
