[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493982
]
dhruba borthakur commented on HADOOP-1298:
------------------------------------------
1. Is there a reason why ClientProtocol.chgrp and ClientProtocol.chown does not
take a ClientContext parameter?
2. Each Inode has a Permissions data structure associated with it. Since most
files will have the same default permissions ("generic", "all") to start with;
can we keep only one copy of the "permissions" in memory and then all inodes
can keep a reference to this common default copy of the permissions. This will
reduce memory consumption of the namenode.
3. I am guessing that the changes to build.xml are purely for debugging and is
not intended for checkin.
> 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
> Attachments: hadoop-user-munncha.patch, hadoop-user-munncha.patch,
> hadoop-user-munncha.patch, hadoop-user-munncha.patch4,
> hadoop-user-munncha.patch5, hadoop-user-munncha.patch6,
> hadoop-user-munncha.patch7, hadoop-user-munncha.patch8,
> hadoop-user-munncha.patch9
>
>
> 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.
