[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525003
]
dhruba borthakur commented on HADOOP-1298:
------------------------------------------
I like the idea of having permissions for directories and not for files. It has
a few advantages:
1. It uses much less memory usage on the namenode.
2. It has precedence: AFS has permissions only on directories
(http://www.cs.unc.edu/cgi-bin/howto?howto=afs-security)
3. Most map-reduce applications deal with directories. A directory is a fileset
and contains files that store related data. All files in a directory are
typically owned by the same user. In this situation, it is sufficient to store
permissions for the entire directory (rather than per file).
> 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.
