Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <27805857.1183688224773.JavaMail.jira@brutus>
Date: Thu, 5 Jul 2007 19:17:04 -0700 (PDT)
From: "Christophe Taton (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1298) adding user info to file
In-Reply-To: <19079061.1177545795510.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christophe Taton commented on HADOOP-1298:
------------------------------------------

I take over Kurtis work on integrating user informations to DFS. I am refactoring the code with the current Hadoop trunk. Here are some details on the current state:
 - New image layout that introduces a user/group database and ownership and access permissions for all files;
 - FileStatus now has a FileAccessRights field containing the owner, group and mode of the file;
 - Owner and group are currently stored as strings, which is not memory efficient unless we share the username and groupname strings between files (or use uid/gid);
 - to provide a compatibility with previous layouts, the user database provides two entries: root:root (to run fsck, for example) and nobody:nogroup (to allow full access to all files to everyone);
 - file modes follow the POSIX octal format (except that the execution right is ignored and turned off);
 - a ClientContext parameter has been added to the operations that require a principal to be executed with; the ClientContext is currently wrapped in the DistributedFileSystem client-side interface, providing some kind of sessions, from the client point of view only.

The ClientContext is currently created on the client side, but should be obtained from the server as a result of a successful authentication. Does a simple password mechanism works for you for now?

Does anybody have some requirements, issues, comments or whatever on this?
I can provide a patch now if someone wants to look more deeply at it, but it is still incomplete and breaks the build of some parts.


> 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.patch10, hadoop-user-munncha.patch11, hadoop-user-munncha.patch12, hadoop-user-munncha.patch13, hadoop-user-munncha.patch14, hadoop-user-munncha.patch15, hadoop-user-munncha.patch16, hadoop-user-munncha.patch17, 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.