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

Madhan Neethiraj resolved RANGER-3920.
--------------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

[~ankita] - thank you for the patch. The fix is now committed in following 
branches:

 
{noformat}
commit 24ea37c2975e41e1322d7ae7079cb6cda239dd71 (HEAD -> master, origin/master, 
origin/HEAD)
Author: Ankita Sinha <[email protected]>
Date:   Tue Oct 11 15:13:41 2022 +0530

    RANGER-3920: when sync'ing users from LDAP, intermittent 
User/Group/UserGroup membership is missing
    
    Signed-off-by: Madhan Neethiraj <[email protected]>
{noformat}

 
{noformat}
commit 377793bb058ee725b26c8c1d5318c17a7f510788 (HEAD -> ranger-2.4, 
origin/ranger-2.4)
Author: Ankita Sinha <[email protected]>
Date:   Tue Oct 11 15:13:41 2022 +0530

    RANGER-3920: when sync'ing users from LDAP, intermittent 
User/Group/UserGroup membership is missing
    
    Signed-off-by: Madhan Neethiraj <[email protected]>
    (cherry picked from commit 24ea37c2975e41e1322d7ae7079cb6cda239dd71)
{noformat}

> When sync'ing users from Ldap,  intermittent User/Group/UserGroup membership  
> is missing
> ----------------------------------------------------------------------------------------
>
>                 Key: RANGER-3920
>                 URL: https://issues.apache.org/jira/browse/RANGER-3920
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin, Ranger, usersync
>            Reporter: Ankita Sinha
>            Assignee: Ankita Sinha
>            Priority: Major
>             Fix For: 3.0.0, 2.4.0
>
>
> Problem Statement:
> Currently, Usersync sync's users/groups/usergroup in batches. In doing so, 
> the user/group/usergroup at the end of the batch is not sync'ed. 
> For example consider batch is of size 1000, so batch starts from 0-999 and  
> then  next batch starts from 1001-1999. So in each batch one 
> user/group/usergroup is missing.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to