[jira] [Updated] (RANGER-3505) Ranger usersync fails to sync users when a duplicate user exists in ranger
[ https://issues.apache.org/jira/browse/RANGER-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Polavarapu updated RANGER-3505: --- Attachment: 0001-RANGER-3505-modified-code-to-ignore-case-while-valid.patch > Ranger usersync fails to sync users when a duplicate user exists in ranger > -- > > Key: RANGER-3505 > URL: https://issues.apache.org/jira/browse/RANGER-3505 > Project: Ranger > Issue Type: Bug > Components: Ranger, usersync >Reporter: Sailaja Polavarapu >Assignee: Sailaja Polavarapu >Priority: Major > Attachments: > 0001-RANGER-3505-modified-code-to-ignore-case-while-valid.patch > > > Ranger is having issue with syncing user with case sensitive when the backend > database for ranger is MySQL / Maria DB. Initially users are sync'd with > default configuration (without any case conversion). Later usersync is > configured to sync users with upper case. At this time, usersync fails to > sync any users throwing duplicate user exception. For resolving this, > existing user from ranger must be deleted and then restarted the usersync > service. Instead, ranger code should update existing user with case > conversion and continue. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 73685: RANGER-3505: Ranger usersync fails to sync users when a duplicate user exists in ranger
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/73685/ --- Review request for ranger, Abhay Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, and Velmurugan Periasamy. Bugs: RANGER-3505 https://issues.apache.org/jira/browse/RANGER-3505 Repository: ranger Description --- modified code to ignore case while validating a user for update Diffs - security-admin/src/main/java/org/apache/ranger/service/XUserService.java f22bcec75 Diff: https://reviews.apache.org/r/73685/diff/1/ Testing --- Patched cluster with Mysql DB as backed for ranger and verified few test cases. Also verified with postgres DB as backend for ranger for quick regression tests. Thanks, Sailaja Polavarapu
[jira] [Commented] (RANGER-2756) A spelling mistake in RangerHiveAuthorizer
[ https://issues.apache.org/jira/browse/RANGER-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438338#comment-17438338 ] Abhishek Kumar commented on RANGER-2756: Hi [~1wc], Could you please close the review request on review board: [https://reviews.apache.org/r/72220] Thanks! > A spelling mistake in RangerHiveAuthorizer > -- > > Key: RANGER-2756 > URL: https://issues.apache.org/jira/browse/RANGER-2756 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: master, 2.0.0, 1.2.0 >Reporter: Wenchao Li >Priority: Trivial > Fix For: 2.1.0 > > Attachments: RANGER-2756.1.patch > > > A spelling mistake was found in RangerHiveAuthorizer's LOG String. > [https://patch-diff.githubusercontent.com/raw/apache/ranger/pull/58.patch] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3505) Ranger usersync fails to sync users when a duplicate user exists in ranger
Sailaja Polavarapu created RANGER-3505: -- Summary: Ranger usersync fails to sync users when a duplicate user exists in ranger Key: RANGER-3505 URL: https://issues.apache.org/jira/browse/RANGER-3505 Project: Ranger Issue Type: Bug Components: Ranger, usersync Reporter: Sailaja Polavarapu Ranger is having issue with syncing user with case sensitive when the backend database for ranger is MySQL / Maria DB. Initially users are sync'd with default configuration (without any case conversion). Later usersync is configured to sync users with upper case. At this time, usersync fails to sync any users throwing duplicate user exception. For resolving this, existing user from ranger must be deleted and then restarted the usersync service. Instead, ranger code should update existing user with case conversion and continue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-3505) Ranger usersync fails to sync users when a duplicate user exists in ranger
[ https://issues.apache.org/jira/browse/RANGER-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Polavarapu reassigned RANGER-3505: -- Assignee: Sailaja Polavarapu > Ranger usersync fails to sync users when a duplicate user exists in ranger > -- > > Key: RANGER-3505 > URL: https://issues.apache.org/jira/browse/RANGER-3505 > Project: Ranger > Issue Type: Bug > Components: Ranger, usersync >Reporter: Sailaja Polavarapu >Assignee: Sailaja Polavarapu >Priority: Major > > Ranger is having issue with syncing user with case sensitive when the backend > database for ranger is MySQL / Maria DB. Initially users are sync'd with > default configuration (without any case conversion). Later usersync is > configured to sync users with upper case. At this time, usersync fails to > sync any users throwing duplicate user exception. For resolving this, > existing user from ranger must be deleted and then restarted the usersync > service. Instead, ranger code should update existing user with case > conversion and continue. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-3414) Release Apache Ranger 2.2.0
[ https://issues.apache.org/jira/browse/RANGER-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani resolved RANGER-3414. - Resolution: Fixed > Release Apache Ranger 2.2.0 > --- > > Key: RANGER-3414 > URL: https://issues.apache.org/jira/browse/RANGER-3414 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > > Release Apache Ranger 2.2.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3498) RANGER : Remove log4j1 dependencies.
[ https://issues.apache.org/jira/browse/RANGER-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mateen N Mansoori updated RANGER-3498: -- Attachment: (was: 0001-RANGER-3498-Remove-log4j1-dependencies.patch) > RANGER : Remove log4j1 dependencies. > > > Key: RANGER-3498 > URL: https://issues.apache.org/jira/browse/RANGER-3498 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Mateen N Mansoori >Priority: Major > > Remove log4j1 dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-3023) Permission tab takes longer time to load with large number of users and group_users data
[
https://issues.apache.org/jira/browse/RANGER-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahesh Hanumant Bandal resolved RANGER-3023.
Fix Version/s: 3.0.0
Resolution: Fixed
committed in master branch, commit id :
[5732060da4c4c88c1fba3c89fa5369ea56c9b942|https://github.com/apache/ranger/commit/5732060da4c4c88c1fba3c89fa5369ea56c9b942]
> Permission tab takes longer time to load with large number of users and
> group_users data
>
>
> Key: RANGER-3023
> URL: https://issues.apache.org/jira/browse/RANGER-3023
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Mahesh Hanumant Bandal
>Assignee: Mahesh Hanumant Bandal
>Priority: Major
> Fix For: 3.0.0
>
>
> GET API /service/xusers/permission takes longer time to load with following
> number of users and group mappings in db.
> {code:java}
> select count(*) from x_user;
> 50052
> select count(*) from x_group_users;
> 500056
> {code}
> Need to have performance optimization on this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (RANGER-3401) Ranger Policy import based on policy guid match
[ https://issues.apache.org/jira/browse/RANGER-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dineshkumar Yadav reassigned RANGER-3401: - Assignee: Pradeep Agrawal (was: Dineshkumar Yadav) > Ranger Policy import based on policy guid match > --- > > Key: RANGER-3401 > URL: https://issues.apache.org/jira/browse/RANGER-3401 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.2.0 >Reporter: Dineshkumar Yadav >Assignee: Pradeep Agrawal >Priority: Major > > Here we will import policies based on policy GUID > 1. If Guid matched then we replace the whole policy as it is from source > otherwise create new policy with same guid. > 2. If there is another policy with same signature at Target we make that > policy as disabled. > 3. Add label to exported policy with cluster name from they are imported -- This message was sent by Atlassian Jira (v8.3.4#803005)
