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

Sailaja Polavarapu updated RANGER-1801:
---------------------------------------
    Attachment: 0001-RANGER-1801-group-user-mapping-updates-to-ranger-adm.patch

Attached the patch for master branch with same changes as ranger-0.7

> group user mapping updates to ranger admin fail when the mapping is already 
> existed in ranger DB.
> -------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1801
>                 URL: https://issues.apache.org/jira/browse/RANGER-1801
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin, Ranger
>            Reporter: Sailaja Polavarapu
>            Assignee: Sailaja Polavarapu
>             Fix For: 1.0.0, 0.7.2
>
>         Attachments: 
> 0001-RANGER-1801-group-user-mapping-updates-to-ranger-adm.patch
>
>
> As part of recent changes for RANGER-1765, db doesn't allow duplicate entries 
> in the x_group_user table. 
> But while adding the entries to x_group_user table, ranger code is not 
> checking if the entry is already existing or not. Because of this the 
> subsequent group membership updates from usersync are failing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to