[
https://issues.apache.org/jira/browse/HADOOP-13102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201033#comment-16201033
]
Anu Engineer commented on HADOOP-13102:
---------------------------------------
+1, I will commit this shortly. Do you need this doc change in 2.x? please let
me know which branches you need this to land and I will cherry-pick them.
Thanks for flagging this for my attention.
> 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
> Labels: docs, ldap
> Attachments: HADOOP-13102-001.patch
>
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
