[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524943
]
eric baldeschwieler commented on HADOOP-1298:
---------------------------------------------
Past experience shows that it is much harder to take something away from a user
community than to never give it to them. It is impossible to predict all the
programmatic interactions with the FS that may be implemented, so I'd suggest
we do the easiest thing to support first, not the most general thing.
What if we store permissions only on directories and only check permissions on
the containing directory?
This seems very easy to document and implement. It would minimize the
permission code that will run in the current critical sections in the namenode
(where performance is a major concern for us) and would give us a lot of
flexibility to distribute the namenodes responsibilities in the future. It
would also reduce the RAM used by permissions by not adding any state to the
file objects...
> 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
> Fix For: 0.15.0
>
> Attachments: 1298_2007-08-30a.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.
