[
https://issues.apache.org/jira/browse/HADOOP-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556026#action_12556026
]
Doug Cutting commented on HADOOP-1873:
--------------------------------------
> The cost of copying a configuration might be too big, so the patch takes the
> first option.
I like the utility methods you've added, but I still worry that they're not
thread-safe. File creation in another thread could get the wrong umask.
The cost of copying a configuration should not be too great, since it mostly
just copies the Properties. Even that could be eliminated by, in
Configuration's copy constructor, replacing 'properties.clone()' with 'new
Properties(properties)'. This is safe, since we do not permit removing
configuration properties nor setting them to null.
Also, you didn't use the new utility method in one of the calls to mkdirs().
Is that intentional?
> 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
>
>
> 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.
