[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526538
]
Raghu Angadi commented on HADOOP-1298:
--------------------------------------
Regd locking : Right now there is no protection around accesses to Namespace
for permission checking. The usual structure for an operation in the patch is :
{code}
checkPermission(path, DELETE); // required access is READ, WRITE etc
delete(path); // or open, etc
{code}
Here {{delete()}} is same as before, which locks the namespace.
I think it could be something like :
{code}
delete() {
// same as before except, just before deleting :
checkPermission(INode.permissions, DELETE);
//...
}
{code}
This ensures access checking an action are consistent.
> 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,
> 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.
