[
https://issues.apache.org/jira/browse/HADOOP-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604302#action_12604302
]
Doug Cutting commented on HADOOP-3536:
--------------------------------------
> Doug, so your suggesting essentially a FileSystem object open for each user
> accessing the DFS?
Yes. FileSystem.get() caches instances based on username, and the RPC system
cache's connections based on username. So applications should not need to do
more than be sure they pass a Configuration that contains the user's
credentials. Currently credentials are set/get in a Configuration only by
UnixUserGroupInformation.java.
> 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.
