[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543666
]
Doug Cutting commented on HADOOP-1298:
--------------------------------------
> I notice permissions are added to all INodes (files and directories) [ ... ]
Here's an important use case: users need to be able to create files that a
daemon user can read but that other users cannot. This is for, e.g., job
submission. How will we implement this? Should the user do something like,
'mkdir D; chgrp mapred_daemon D; chmod g+r D; chmod o-r D; cp job.xml D'? Can
D's parent directory belong to mapred_daemon? Currently this is done in the
mapred 'system' directory, which would be owned by mapred_daemon. This is
nice, since we'd like the daemon to be able to, e.g., clear the directory on
restart.
Would this be made any easier if we could assign permissions to files and not
just directories?
> adding user info to file
> ------------------------
>
> Key: HADOOP-1298
> URL: https://issues.apache.org/jira/browse/HADOOP-1298
> Project: Hadoop
> Issue Type: New Feature
> Components: dfs, fs
> Reporter: Kurtis Heimerl
> Assignee: Christophe Taton
> Attachments: 1298_2007-09-22_1.patch, 1298_2007-10-04_1.patch,
> 20071116b.patch, hadoop-user-munncha.patch17
>
>
> I'm working on adding a permissions model to hadoop's DFS. The first step is
> this change, which associates user info with files. Following this I'll
> assoicate permissions info, then block methods based on that user info, then
> authorization of the user info.
> So, right now i've implemented adding user info to files. I'm looking for
> feedback before I clean this up and make it offical.
> I wasn't sure what release, i'm working off trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
