[
https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607340#action_12607340
]
Craig Macdonald commented on HADOOP-3536:
-----------------------------------------
In all cases, sometimes a process will need to have an 'asuser' privilege -
which mean it needs to access the DFS as other arbitrary users. Perhaps the
libhdfs API would not need to change in the future, but the implementation to
support the permissions may change.
The crucial point is how does Hadoop tell if the current user has the 'asuser'
privilege.
Also, I'm using uid_t/gid_t to designate a user, (char* username, char**
groupnames) would be OK by me as well.
C
> 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.
