ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailaja Polavarapu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-1801) group user mapping updates to ranger admin fail when the mapping is already existed in ranger DB.
Date Tue, 26 Sep 2017 20:51:00 GMT

    [ https://issues.apache.org/jira/browse/RANGER-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181547#comment-16181547
] 

Sailaja Polavarapu commented on RANGER-1801:
--------------------------------------------

Review request available at:
https://reviews.apache.org/r/62555/

> 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
>
>
> 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)

Mime
View raw message