[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533490
]
Sameer Paranjpye commented on HADOOP-1298:
------------------------------------------
Why do we need a user.database.file in the configuration?
The username -> userid, groupname -> groupid mapping should be completely
internal to the Namenode. Is there any reason that these ids cannot be
completely internal to the Namenode? The user database would primarily be a
space conservation tool which would enable us to refer to users and groups by
id in the serialized fsimage and in memory. The Namenode would generate a new
userid when it encounters a username it hasn't seen before. The 'user database'
would be serialized at the front of the image.
Requiring a file with a username -> id mapping that admins need to manage is
brittle. In addition, as Allen points out requiring an fs restart for user
additions is unsustainable.
> 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-09-22_1.patch, 1298_2007-10-04_1.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.
