Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <105790444.1214245365247.JavaMail.jira@brutus>
Date: Mon, 23 Jun 2008 11:22:45 -0700 (PDT)
From: "Craig Macdonald (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (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:all-tabpanel ]

Craig Macdonald updated HADOOP-3536:
------------------------------------

    Attachment: getlogininfo.c

Code to determine:
 * uid -> username
 * uid -> username,all groupnames

This code could be used to set the hadoop.job.ugi property to obtain the correct FileSystem object for each user accessing the DFS.

> 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
>         Attachments: getlogininfo.c
>
>
> 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.