Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <4820137.1214245125132.JavaMail.jira@brutus>
Date: Mon, 23 Jun 2008 11:18:45 -0700 (PDT)
From: "Craig Macdonald (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3536) Support permissions in fuse-dfs
In-Reply-To: <805796842.1213206886753.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-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607327#action_12607327 ] 

Craig Macdonald commented on HADOOP-3536:
-----------------------------------------

Ok, this would require some minor changes in libhdfs API.

Currently, the connection API is:
[noformat]
hdfsFS hdfsConnect(const char* host, tPort port);
[noformat]

I suggest adding one or two additional API calls, to allow connection as a given user:
[noformat]
/** 
  * hdfsConnect - Connect to a hdfs file system as the specified user, and all
  * of his/her groups
  */
hdfsFS hdfsConnect(const char* host, tPort port, uid_t uid);

/** 
  * hdfsConnect - Connect to a hdfs file system as the specified user, and only the specified group
  */
hdfsFS hdfsConnect(const char* host, tPort port, uid_t uid, gid_t gid);

[noformat]

This would require libhdfs to achieve two tasks:
 * For  a given uid, determine the username and all his/her groups (names), and use these to access a FileSystem object
 * For a given uid, determine the username and the group names

Code to achieve this attached.


> Support permissions in fuse-dfs
> -------------------------------
>
>                 Key: HADOOP-3536
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3536
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: contrib/fuse-dfs
>            Reporter: Craig Macdonald
>
> Currently permissions are unsupported by fuse-dfs.
> This manifests itself as two issues:
>  * Users accessing a fuse-dfs mount do so as the user running fuse_dfs executable. In this case, it would be better to run fuse-dfr as some privileged user, and use Hadoop API calls determine whether the current user was privileged enough to perform the action.
>  * Users cannot view/change permissions on the mounted volume. See  HADOOP-3264

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.