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 18:21:06 GMT

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

Aaron T. Myers commented on HADOOP-7214:
----------------------------------------

Thanks for the review, Nicholas.

bq. You are right that NN and JT are doing group resolution but they are not the group service
provider. So, it may be better to let the command to directly invoke service provider (e.g.
LDAP, Unix shell, etc.) What do you think?

I'm not sure I understand the suggestion. Is your point that the FsShell should just directly
invoke the configured {{GroupMappingServiceProvider}}, instead of making an RPC? The reason
I went the RPC route is precisely to account for the case that there are different sets of
users/groups on the client vs. the NN or JT.

> 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,
hadoop-7214.4.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

Mime
View raw message