[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:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.1.0
3.0.0
2.9.0
Status: Resolved (was: Patch Available)
[~ekundin] Thanks for the contribution. I have committed this to trunk,
branch-3.0, and branch-2.
[~subru] Thanks for reminding me to commit this Jira. I appreciate it.
> 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
> Fix For: 2.9.0, 3.0.0, 3.1.0
>
> 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}
> hadoop.security.group.mapping.ldap.search.group.hierarchy.levels
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[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
]
Arun Suresh updated HADOOP-13102:
-
Is this still on target for 2.9.0 ? If not, can we we push this out to the next
major release ?
> 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}
> hadoop.security.group.mapping.ldap.search.group.hierarchy.levels
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[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
]
Junping Du updated HADOOP-13102:
Target Version/s: 2.9.0 (was: 2.8.0)
Fix Version/s: (was: 2.8.0)
The patch is not get in, so we should set target version instead of fix
version. 2.8.0 is in releasing, reset to 2.9 instead.
> 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}
> hadoop.security.group.mapping.ldap.search.group.hierarchy.levels
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[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
]
Esther Kundin updated HADOOP-13102:
---
Attachment: HADOOP-13102-001.patch
> 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
> Fix For: 2.8.0
>
> 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}
> hadoop.security.group.mapping.ldap.search.group.hierarchy.levels
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[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
]
Esther Kundin updated HADOOP-13102:
---
Labels: docs ldap (was: )
Status: Patch Available (was: In Progress)
> 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
> Fix For: 2.8.0
>
> 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}
> hadoop.security.group.mapping.ldap.search.group.hierarchy.levels
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[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}
hadoop.security.group.mapping.ldap.search.group.hierarchy.levels
{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}
hadoop.security.group.mapping.ldap.search.group.hierarchy.levels
{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}
> hadoop.security.group.mapping.ldap.search.group.hierarchy.levels
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
