You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Anu Engineer (JIRA)" <ji...@apache.org> on 2016/05/05 16:56:12 UTC
[jira] [Updated] (HADOOP-13102) Update GroupsMapping documentation
to reflect the new changes
[ https://issues.apache.org/jira/browse/HADOOP-13102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anu Engineer updated HADOOP-13102:
----------------------------------
Description:
We need to update this section in the groupsMapping.md
{noformat}
Line 84:
The implementation does not attempt to resolve group hierarchies. Therefore, a user must be an explicit member of a group object
in order to be considered a member.
{noformat}
With changes in Hadoop-12291 this is no longer true since we will have the ability to walk the group hierarchies.
We also should modify this line
{noformat}
Line : 81
It is possible to set a maximum time limit when searching and awaiting a result.
Set `hadoop.security.group.mapping.ldap.directory.search.timeout` to 0 if infinite wait period is desired. Default is 10,000 milliseconds (10 seconds).
{noformat}
we might want to document how the new settings affects the timeout.
and also add the new settings into this doc.
{noformat}
<name>hadoop.security.group.mapping.ldap.search.group.hierarchy.levels</name>
{noformat}
was:
We need to update this section in the groupsMapping.md
{noformat}
Line 84:
The implementation does not attempt to resolve group hierarchies. Therefore, a user must be an explicit member of a group object
in order to be considered a member.
{noformat}
With changes in Hadoop-12291 this is no longer true since we will have the ability to walk the group hierarchies.
We also should modify this line
{noformat}
Line : 81
It is possible to set a maximum time limit when searching and awaiting a result.
Set `hadoop.security.group.mapping.ldap.directory.search.timeout` to 0 if infinite wait period is desired. Default is 10,000 milliseconds (10 seconds).
{noformat}
we might want to document how the new settings affects the timeoout.
and also add the new settings into this doc.
{noformat}
<name>hadoop.security.group.mapping.ldap.search.group.hierarchy.levels</name>
{noformat}
> Update GroupsMapping documentation to reflect the new changes
> -------------------------------------------------------------
>
> Key: HADOOP-13102
> URL: https://issues.apache.org/jira/browse/HADOOP-13102
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation
> Affects Versions: 2.8.0
> Reporter: Anu Engineer
> Assignee: Esther Kundin
> Fix For: 2.8.0
>
>
> We need to update this section in the groupsMapping.md
> {noformat}
> Line 84:
> The implementation does not attempt to resolve group hierarchies. Therefore, a user must be an explicit member of a group object
> in order to be considered a member.
> {noformat}
> With changes in Hadoop-12291 this is no longer true since we will have the ability to walk the group hierarchies.
> We also should modify this line
> {noformat}
> Line : 81
> It is possible to set a maximum time limit when searching and awaiting a result.
> Set `hadoop.security.group.mapping.ldap.directory.search.timeout` to 0 if infinite wait period is desired. Default is 10,000 milliseconds (10 seconds).
> {noformat}
> we might want to document how the new settings affects the timeout.
> and also add the new settings into this doc.
> {noformat}
> <name>hadoop.security.group.mapping.ldap.search.group.hierarchy.levels</name>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org