[
https://issues.apache.org/jira/browse/HADOOP-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hairong Kuang updated HADOOP-1873:
----------------------------------
Attachment: mapred6.patch
Mmm...Copying configuration still does not work. Any change to the copied
configuration is not visible to the file system handler. In order for the
change to take effect, we have to close the file system handle (so it is
removed from FileSystem cache and then refetch it. So the mkdirs code looks
like:
{noformat}
public static boolean mkdirs(FileSystem fs, Path dir, FsPermission permission)
throws IOException {
Configuration conf = new Configuration(fs.getConf());
conf.setInt(FsPermission.UMASK_LABEL, 0);
fs.close();
fs = FileSystem.get(conf);
return fs.mkdirs(dir, permission);
}
{noformat}
But closing the file handler is not acceptable and refeching a new file system
handler is too expensive. The attached patch reverts to option 1.
> 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.
