[ 
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christophe Taton updated HADOOP-1298:
-------------------------------------

    Attachment: 1298_20070821c-1298only.patch
                1298_20070821c-full.patch

Update to follow the trunk and to integrate some remarks.
- on file creation, implicit mkdirs() only if directory does not exist 
(implicit mkdirs() might be done on the server side, to prevent many RPCs for a 
single operation?): this change is required as implicitly creating already 
existing directories requires creation permissions for these directories.
- redesign of the POSIX permission check to conform to the new INodes (does not 
use INode.parent anymore, to allow its future removal)
- added INode.permissions field, with getter/setter
- added INode[] INodeDirectory.getExistingINodes(String path) and int 
INodeDirectory.getExistingINodes(String[] components, INode[] existing) methods 
to retrieve the existing INodes that compose a path in the tree.


> 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_20070821c-1298only.patch, 
> 1298_20070821c-full.patch, hadoop-user-munncha.patch17, layout20070731.patch
>
>
> 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.

Reply via email to