[GitHub] [ranger] dependabot[bot] opened a new pull request, #197: Bump certifi from 2022.6.15 to 2022.12.7 in /ranger-tools/src/main/python

dependabot[bot] opened a new pull request, #197: URL: https://github.com/apache/ranger/pull/197 Bumps [certifi](https://github.com/certifi/python-certifi) from 2022.6.15 to 2022.12.7. Commits https://github.com/certifi/python-certifi/commit/9e9e840925d7b8e76c76fdac1fab7e6e88c1c

Re: Review Request 74242: RANGER-4009: Open read access to some Policy Engine objects and metrics

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74242/#review224988 --- agents-common/src/main/java/org/apache/ranger/plugin/policyengine

Re: Review Request 74242: RANGER-4009: Open read access to some Policy Engine objects and metrics

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74242/ --- (Updated Dec. 9, 2022, 4:37 a.m.) Review request for ranger, madhan, Madhan Nee

[jira] [Updated] (RANGER-4009) Open read access to some Policy Engine objects and metrics

[ https://issues.apache.org/jira/browse/RANGER-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhay Kulkarni updated RANGER-4009: --- Summary: Open read access to some Policy Engine objects and metrics (was: Open access to so

[jira] [Created] (RANGER-4009) Open access to some Policy Engine objects and metrics

Abhay Kulkarni created RANGER-4009: -- Summary: Open access to some Policy Engine objects and metrics Key: RANGER-4009 URL: https://issues.apache.org/jira/browse/RANGER-4009 Project: Ranger Is

[jira] [Assigned] (RANGER-4009) Open access to some Policy Engine objects and metrics

[ https://issues.apache.org/jira/browse/RANGER-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhay Kulkarni reassigned RANGER-4009: -- Assignee: Abhay Kulkarni > Open access to some Policy Engine objects and metrics > --

Re: Review Request 74243: RANGER-4004: During the service deletion also, we can clear the in-memory cache for that service which got deleted on the ranger side

> On Dec. 9, 2022, 2:40 a.m., Madhan Neethiraj wrote: > > security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBStore.java > > Lines 1411 (patched) > > > > > > I guess you meant to add the following after

Re: Review Request 74243: RANGER-4004: During the service deletion also, we can clear the in-memory cache for that service which got deleted on the ranger side

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74243/ --- (Updated Dec. 9, 2022, 3:38 a.m.) Review request for ranger, Don Bosco Durai, A

Re: Review Request 74243: RANGER-4004: During the service deletion also, we can clear the in-memory cache for that service which got deleted on the ranger side

> On Dec. 9, 2022, 2:40 a.m., Madhan Neethiraj wrote: > > security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBStore.java > > Lines 1411 (patched) > > > > > > I guess you meant to add the following after

Re: Review Request 74243: RANGER-4004: During the service deletion also, we can clear the in-memory cache for that service which got deleted on the ranger side

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74243/#review224985 --- security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBS

Re: Review Request 74238: RANGER-4007: HDFS Authorizer changes to take advantage of support for multiple access-types in the Ranger Access Request

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74238/#review224984 --- Ship it! Ship It! - Ramesh Mani On Dec. 8, 2022, 9:25 p.m.,

Re: Review Request 74248: RANGER-4008: updated RangerTagEnricher to ignore invalid resources

> On Dec. 8, 2022, 11:38 p.m., Abhay Kulkarni wrote: > > agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagEnricher.java > > Line 435 (original), 434 (patched) > > > > > > In the flow - ta

Re: Review Request 74248: RANGER-4008: updated RangerTagEnricher to ignore invalid resources

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74248/#review224982 --- Fix it, then Ship it! agents-common/src/main/java/org/apache/r

[jira] [Updated] (RANGER-4008) RangerTagEnricher to ignore invalid resources

[ https://issues.apache.org/jira/browse/RANGER-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated RANGER-4008: - Attachment: RANGER-4008.patch > RangerTagEnricher to ignore invalid resources >

Review Request 74248: RANGER-4008: updated RangerTagEnricher to ignore invalid resources

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74248/ --- Review request for ranger, Ankita Sinha, Kishor Gollapalliwar, Abhay Kulkarni, M

[jira] [Created] (RANGER-4008) RangerTagEnricher to ignore invalid resources

Madhan Neethiraj created RANGER-4008: Summary: RangerTagEnricher to ignore invalid resources Key: RANGER-4008 URL: https://issues.apache.org/jira/browse/RANGER-4008 Project: Ranger Issue

Re: Review Request 74238: RANGER-4007: HDFS Authorizer changes to take advantage of support for multiple access-types in the Ranger Access Request

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74238/ --- (Updated Dec. 8, 2022, 9:25 p.m.) Review request for ranger, madhan, Madhan Nee

[jira] [Created] (RANGER-4007) HDFS Authorizer changes to take advantage of support for multiple access-types in the Ranger Access Request

Abhay Kulkarni created RANGER-4007: -- Summary: HDFS Authorizer changes to take advantage of support for multiple access-types in the Ranger Access Request Key: RANGER-4007 URL: https://issues.apache.org/jira/brows

[jira] [Updated] (RANGER-3537) Find a viable replacement of Backbone JS for Ranger UI.

[ https://issues.apache.org/jira/browse/RANGER-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dhaval Rajpara updated RANGER-3537: --- Attachment: 0001-RANGER-3537.patch > Find a viable replacement of Backbone JS for Ranger UI.

[ANNOUNCE] Apache Ranger UI using React JS [Initial implementation]

Hi Ranger Community, An initial implementation of RANGER-3537 (Migrate Ranger UI from outdated backbone JS to React JS) is ready for your review. Kindly request you to review/test and provide your feedback. Please find the review request link:

Review Request 74246: RANGER-3537 : Find a viable replacement of Backbone JS for Ranger UI.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74246/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Brijesh Bhalala, Dhava

Re: Review Request 74247: RANGER-4005:Add support in ranger to return the list of roles in which given role is associated

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74247/ --- (Updated Dec. 8, 2022, 8:37 p.m.) Review request for ranger, Don Bosco Durai, A

[jira] [Updated] (RANGER-4005) Add support in ranger to return the list of roles in which given role is associated

[ https://issues.apache.org/jira/browse/RANGER-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Purbhe updated RANGER-4005: -- Affects Version/s: 2.3.0 > Add support in ranger to return the list of roles in which given ro

[jira] [Updated] (RANGER-4005) Add support in ranger to return the list of roles in which given role is associated

[ https://issues.apache.org/jira/browse/RANGER-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Purbhe updated RANGER-4005: -- Fix Version/s: 3.0.0 > Add support in ranger to return the list of roles in which given role i

[jira] [Updated] (RANGER-4005) Add support in ranger to return the list of roles in which given role is associated

[ https://issues.apache.org/jira/browse/RANGER-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Purbhe updated RANGER-4005: -- Attachment: RANGER-4005-Add-support-in-ranger-to-return-the-list.patch > Add support in ranger

[jira] [Commented] (RANGER-3373) Ranger Hbase plugin not compatible with Hbase 2.3.4

[ https://issues.apache.org/jira/browse/RANGER-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644820#comment-17644820 ] Joseph Wheeler commented on RANGER-3373: Issue appears in Ranger 2.3.0 with HBas

[jira] [Commented] (RANGER-4005) Add support in ranger to return the list of roles in which given role is associated

[ https://issues.apache.org/jira/browse/RANGER-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644819#comment-17644819 ] Nikhil Purbhe commented on RANGER-4005: --- Pull request : https://reviews.apache.org

Review Request 74247: RANGER-4005:Add support in ranger to return the list of roles in which given role is associated

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74247/ --- Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, Me

Review Request 74245: RANGER-3899:Policy creation takes more time when there are more users, groups, roles

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74245/ --- Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, Me

[jira] [Updated] (RANGER-3899) Policy creation takes more time when there are more users,groups,roles

[ https://issues.apache.org/jira/browse/RANGER-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramachandran updated RANGER-3899: - Summary: Policy creation takes more time when there are more users,groups,roles (was: Policy cr

[jira] [Updated] (RANGER-3899) Policy creation takes more time when there are more users

[ https://issues.apache.org/jira/browse/RANGER-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramachandran updated RANGER-3899: - Description: *{color:#ff}Policy Creation Steps in Apache Ranger:{color}*{color:#ff}  {co

[jira] [Updated] (RANGER-3899) Policy creation takes more time when there are more users

[ https://issues.apache.org/jira/browse/RANGER-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramachandran updated RANGER-3899: - Description: *{color:#ff}Policy Creation Steps in Apache Ranger:{color}*{color:#ff}  {co

[jira] [Created] (RANGER-4006) Add Bulk create update delete API in Ranger

Nikhil Purbhe created RANGER-4006: - Summary: Add Bulk create update delete API in Ranger Key: RANGER-4006 URL: https://issues.apache.org/jira/browse/RANGER-4006 Project: Ranger Issue Type: Ne

[jira] [Assigned] (RANGER-3899) Policy creation takes more time when there are more users

[ https://issues.apache.org/jira/browse/RANGER-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramachandran reassigned RANGER-3899: Assignee: Ramachandran > Policy creation takes more time when there are more users > ---

[jira] [Created] (RANGER-4005) Add support in ranger to return the list of roles in which given role is associated

Nikhil Purbhe created RANGER-4005: - Summary: Add support in ranger to return the list of roles in which given role is associated Key: RANGER-4005 URL: https://issues.apache.org/jira/browse/RANGER-4005

Re: Review Request 74243: RANGER-4004: During the service deletion also, we can clear the in-memory cache for that service which got deleted on the ranger side

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74243/ --- (Updated Dec. 8, 2022, 11:48 a.m.) Review request for ranger, Don Bosco Durai,

Re: Review Request 74112: RANGER-3903 : Bug in RangerPolicyDeltaUtil--> applyDeltas method

> On Sept. 19, 2022, 1:24 a.m., Abhay Kulkarni wrote: > > agents-common/src/main/java/org/apache/ranger/plugin/util/RangerPolicyDeltaUtil.java > > Line 113 (original), 108 (patched) > > > > > > For a deleted policy,

[GitHub] [ranger] Hoo199212 commented on pull request #186: RANGER-3968:The plugin cannot download the latest policy

Hoo199212 commented on PR #186: URL: https://github.com/apache/ranger/pull/186#issuecomment-1342329813 @mneethiraj Hi,Ranger cannot completely rely on the stability of the database, so it is necessary to add the timeout, but the timeout needs to be discussed -- This is an automated messa

[jira] [Commented] (RANGER-4004) During the service deletion also, we can clear the in-memory cache for that service which got deleted on the ranger side

[ https://issues.apache.org/jira/browse/RANGER-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644679#comment-17644679 ] Ramachandran commented on RANGER-4004: -- [~madhan]  The review is available here :ht

[jira] [Updated] (RANGER-4004) During the service deletion also, we can clear the in-memory cache for that service which got deleted on the ranger side

[ https://issues.apache.org/jira/browse/RANGER-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramachandran updated RANGER-4004: - Attachment: 0001-RANGER-4004-During-the-service-deletion-also-we-can-.patch > During the service

Review Request 74243: RANGER-4004: During the service deletion also, we can clear the in-memory cache for that service which got deleted on the ranger side

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74243/ --- Review request for ranger, Don Bosco Durai, Abhay Kulkarni, Madhan Neethiraj, Me