[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Taton updated HADOOP-1298:
-------------------------------------
Attachment: 1298_2007-09-22_1.patch
Here is a new patch. Permissions are now represented:
- with user IDs internally (server-side)
- with user names externally (client-side)
I updated the web interface and the command-line {{FsShell}} to display
permissions as a 9 characters string (rwxrwxrwx) and user names (instead of
IDs).
The user database is stored in a static properties file which follows the
format: {{<username>:<user id>}}. This properties file name is defined in
{{hadoop-site.xml}} with the configuration property {{user.database.file}}
which will by default refer to a file named "{{userdb.properties}}". There is
no user management in this implementation.
JUnit tests are fine here.
This still lacks an automatic setting of ownership when upgrading for
{{/user/<username>}} 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
> Fix For: 0.15.0
>
> Attachments: 1298_2007-09-06b.patch, 1298_2007-09-07g.patch,
> 1298_2007-09-22_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.
