[
https://issues.apache.org/jira/browse/HDFS-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004139#comment-14004139
]
Aaron T. Myers commented on HDFS-6435:
--------------------------------------
I should also mention that I just did some manual testing between a client
machine with a completely different set of UIDs/GIDs from the machine running
the NFS Gateway, and this feature works as expected once the static mapping
file is configured correctly. In my case, I used the following mapping file,
and while browsing HDFS over NFS was able to see the correct user/group names
displayed:
{noformat}
$ cat /etc/nfs.map
uid 1037 1000 # atm
gid 516 1000 # atm
uid 17 115 # hdfs
gid 18 125 # hdfs
gid 23 999 # supergroup
{noformat}
> Add support for specifying a static uid/gid mapping for the NFS gateway
> -----------------------------------------------------------------------
>
> Key: HDFS-6435
> URL: https://issues.apache.org/jira/browse/HDFS-6435
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: nfs
> Affects Versions: 2.4.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: HDFS-6435.patch
>
>
> It's quite reasonable that folks will want to access the HDFS NFS Gateway
> from client machines where the UIDs/GIDs do not line up with those on the NFS
> Gateway itself. We should provide a way to map these UIDs/GIDs between the
> systems.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
