hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-6527) UserGroupInformation::createUserForTesting clobbers already defined group mappings
Date Thu, 05 Jul 2012 23:25:35 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tsz Wo (Nicholas), SZE updated HADOOP-6527:
-------------------------------------------

    Hadoop Flags: Reviewed

+1 patch looks good.
                
> UserGroupInformation::createUserForTesting clobbers already defined group mappings
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-6527
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6527
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Jakob Homan
>            Assignee: Ivan Mitic
>         Attachments: HADOOP-6527-branch-1-win_UGI_fix(2).patch, HADOOP-6527-branch-1-win_UGI_fix.patch
>
>
> In UserGroupInformation::createUserForTesting the follow code creates a new groups instance,
obliterating any groups that have been previously defined in the static groups field.
> {code}    if (!(groups instanceof TestingGroups)) {
>       groups = new TestingGroups();
>     }
> {code}
> This becomes a problem in tests that start a Mini{DFS,MR}Cluster and then create a testing
user.  The user that started the user (generally the real user running the test) immediately
has their groups wiped out and is prevented from accessing files/folders/queues they should
be able to.  Before the UserGroupInformation.createRemoteUserForTesting, calls to userA.getGroups
may return {"a", "b", "c"} and immediately after the new fake user is created, the same call
will return an empty array.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message