[
https://issues.apache.org/jira/browse/MAPREDUCE-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Gummadi updated MAPREDUCE-2416:
------------------------------------
Attachment: 2416.patch
Attaching patch that removes the restriction of specifying groups of each user
in the users-list-file of RoundRobinUserResolver.
With this patch, the new format of each line of the users-list-file is
{code}
username[,group]*
{code}
[,group]* is just to allow older users-list-files for backward compatibility.
Later, may be in the next release, we can fully remove the groups from
users-list-file.
This patch is on top of the patch of MAPREDUCE-2417.
> In Gridmix, in RoundRobinUserResolver, the list of groups for a user obtained
> from users-list-file is incorrect
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-2416
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2416
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/gridmix
> Reporter: Ravi Gummadi
> Assignee: Ravi Gummadi
> Attachments: 2416.patch
>
>
> RoundRobinUserResolver.parseUserList() has a bug in obtaining list of groups
> for each user --- in the sense that the list is not cleared before obtaining
> groups list for the next user. So if the first line has some groups, then
> from 2nd
> line onwards, the validation of "whether the users(in the next lines) are
> also having group names in those lines" is useless as the list is already
> nonempty.
> For example, users-list-file content as shown below also is valid as per
> parseUserList():
> ------------------
> user1,group1
> user2,
> user3,
> user4,
> ------------------
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
