hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7214) Hadoop /usr/bin/groups equivalent
Date Thu, 14 Apr 2011 21:14:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020034#comment-13020034

Aaron T. Myers commented on HADOOP-7214:

bq. Here is more details: NN and JT resolve groups by invoking the configured GroupMappingServiceProvider,
which might connect to another group server (e.g. LDAP). Could the shell command use the same
configuration to obtain GroupMappingServiceProvider so that it could talk to the group server

That at least won't work in the case of the default configuration, i.e. using {{ShellBasedUnixGroupsMapping}}.
In this case the groups a user belongs to are determined simply by shelling out to `{{id -Gn
<username>}}'. If that were run on the client machine, it might get the wrong groups
for the user.

> Hadoop /usr/bin/groups equivalent
> ---------------------------------
>                 Key: HADOOP-7214
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7214
>             Project: Hadoop Common
>          Issue Type: New Feature
>    Affects Versions: 0.23.0
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>         Attachments: hadoop-7214.0.txt, hadoop-7214.1.txt, hadoop-7214.2.txt, hadoop-7214.3.txt,
> Since user -> groups resolution is done on the NN and JT machines, there should be
a way for users to determine what groups they're a member of from the NN's and JT's perspective.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message