[jira] [Resolved] (RANGER-4438) Read JAVA_OPTS in ranger db setup python script
[ https://issues.apache.org/jira/browse/RANGER-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj resolved RANGER-4438. -- Resolution: Fixed > Read JAVA_OPTS in ranger db setup python script > --- > > Key: RANGER-4438 > URL: https://issues.apache.org/jira/browse/RANGER-4438 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4438.patch, RANGER-4438-2.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4438) Read JAVA_OPTS in ranger db setup python script
[
https://issues.apache.org/jira/browse/RANGER-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789946#comment-17789946
]
Madhan Neethiraj commented on RANGER-4438:
--
[Patch|https://reviews.apache.org/r/74757/] committed:
{noformat}
commit 6c26045215454cd90c36b0f33205edab6751 (HEAD -> master, origin/master,
origin/HEAD)
Author: Madhan Neethiraj
Date: Sat Nov 25 02:27:28 2023 -0800
RANGER-4438: fixed setup scripts to not require java_opts in
install.properties
{noformat}
> Read JAVA_OPTS in ranger db setup python script
> ---
>
> Key: RANGER-4438
> URL: https://issues.apache.org/jira/browse/RANGER-4438
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-4438.patch, RANGER-4438-2.patch
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4560) Ranger Roles Cache improvement to reduce DB calls to the Database
[ https://issues.apache.org/jira/browse/RANGER-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramachandran updated RANGER-4560: - Attachment: 0001-RANGER-4560-Ranger-Roles-Cache-improvement-to-reduce.patch > Ranger Roles Cache improvement to reduce DB calls to the Database > - > > Key: RANGER-4560 > URL: https://issues.apache.org/jira/browse/RANGER-4560 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Ramachandran >Assignee: Ramachandran >Priority: Major > Attachments: > 0001-RANGER-4560-Ranger-Roles-Cache-improvement-to-reduce.patch > > > How Ranger uses the Roles Cache (In-Memory) > When the lastKnownRoleVersion and rangerRoleVersionInDB are equal then return > null. Because roles have not changed since the last time > otherwise, It will fetch the roles from the Database update the cache, and > then return roles to the User/Ranger Plugins > As part of Ranger Roles Cache improvement, we have added the below logic > When the rolesVersionInDB and cachedRolesVersion are equal then return cached > RangerRoles.Because RangerRoles have not changed since the last time we > fetched > How it will improve the Ranger Roles Cache > When the user/Client(Ranger Plugin) sends the lastKnownRoleVersion as -1 or > null, Ranger Roles Cache internally check whether rolesVersionInDB and > cachedRolesVersion are equal or not ?. If it equal means, it will fetch it > from the Cache rather than fetching the roles from the database update the > cache, and then return roles to the User/Ranger Plugins -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4561) Adding the mechanism to eanble/disable Ranager Access logs based on property
[ https://issues.apache.org/jira/browse/RANGER-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramachandran updated RANGER-4561: - Attachment: 0001-RANGER-4561-Adding-the-mechanism-to-eanble-disable-R.patch > Adding the mechanism to eanble/disable Ranager Access logs based on property > - > > Key: RANGER-4561 > URL: https://issues.apache.org/jira/browse/RANGER-4561 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Ramachandran >Assignee: Ramachandran >Priority: Major > Attachments: > 0001-RANGER-4561-Adding-the-mechanism-to-eanble-disable-R.patch > > > In the current Ranger Admin, we have enabled Ranger access logs by default. > If any of the customers wants to disable, the Ranger access logs, it can not > be done without making code changes.So we need to leverage this use case so > that customers can disable the ranger access logs if they needed via setting > properties -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74757: RANGER-4438: fixed setup scripts to not require java_opts in install.properties
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74757/#review226004 --- Ship it! Ship It! - Pradeep Agrawal On Nov. 25, 2023, 7:08 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74757/ > --- > > (Updated Nov. 25, 2023, 7:08 p.m.) > > > Review request for ranger, Ankita Sinha, Abhay Kulkarni, Monika Kachhadiya, > Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Subhrat Chaudhary, and > Velmurugan Periasamy. > > > Bugs: RANGER-4438 > https://issues.apache.org/jira/browse/RANGER-4438 > > > Repository: ranger > > > Description > --- > > updated setup.sh of Ranger admin and KMS to not fail the setup when java_opts > is not present in install.properties > > > Diffs > - > > kms/scripts/setup.sh e64c32aa1 > security-admin/scripts/setup.sh ee53d873b > > > Diff: https://reviews.apache.org/r/74757/diff/1/ > > > Testing > --- > > - verified that setup of Ranger admin and KMS succeed even when java_opts is > not present in install.properties > > > Thanks, > > Madhan Neethiraj > >
[jira] [Updated] (RANGER-3722) Fix Test-case failure
[ https://issues.apache.org/jira/browse/RANGER-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-3722: - Fix Version/s: 3.0.0 > Fix Test-case failure > - > > Key: RANGER-3722 > URL: https://issues.apache.org/jira/browse/RANGER-3722 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-3722-Fix-Test-case-failure.patch > > > Below Test-case fail when we use maven surefire report plugins: > > test49importPoliciesFromFileAllowingOverride(org.apache.ranger.rest.TestServiceREST) > Time elapsed: 0.157 sec <<< ERROR! > java.io.FileNotFoundException: > ./src/test/java/org/apache/ranger/rest/importPolicy/import_policy_test_file.json > (No such file or directory) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.(FileInputStream.java:138) > at > org.apache.ranger.rest.TestServiceREST.test49importPoliciesFromFileAllowingOverride(TestServiceREST.java:1703) > > test50importPoliciesFromFileNotAllowingOverride(org.apache.ranger.rest.TestServiceREST) > Time elapsed: 0.003 sec <<< ERROR! > java.io.FileNotFoundException: > ./src/test/java/org/apache/ranger/rest/importPolicy/import_policy_test_file.json > (No such file or directory) > at java.io.FileInputStream.open0(Native Method) > at java.io.FileInputStream.open(FileInputStream.java:195) > at java.io.FileInputStream.(FileInputStream.java:138) > at > org.apache.ranger.rest.TestServiceREST.test50importPoliciesFromFileNotAllowingOverride(TestServiceREST.java:1768) > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4524) FIx TestRangerMetricsContainerSource class UT
[
https://issues.apache.org/jira/browse/RANGER-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789919#comment-17789919
]
Bhavik Patel commented on RANGER-4524:
--
Commit link:
https://github.com/apache/ranger/commit/c7573d06726e42ced28f3e124095ab531c93b75b
> FIx TestRangerMetricsContainerSource class UT
> -
>
> Key: RANGER-4524
> URL: https://issues.apache.org/jira/browse/RANGER-4524
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Bhavik Patel
>Assignee: Bhavik Patel
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-4524-Fix-TestRangerMetricsContainerSource-cla.patch
>
>
> Steps to reproduce:
> 1. clean .m2 repo and trigger the test-cases.
> {code:java}
> java.lang.NoClassDefFoundError: org/apache/log4j/Level at
> org.apache.ranger.metrics.source.TestRangerMetricsContainerSource.init(TestRangerMetricsContainerSource.java:46)
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Level at
> org.apache.ranger.metrics.source.TestRangerMetricsContainerSource.init(TestRangerMetricsContainerSource.java:46){code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Review Request 74760: RANGER-4563: Upgrade Jetty-client version to 9.4.53.v20231009
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74760/ --- Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Kirby Zhou, Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, and Vishal Suvagia. Bugs: RANGER-4563 https://issues.apache.org/jira/browse/RANGER-4563 Repository: ranger Description --- Upgrade Jetty-client version to 9.4.53.v20231009 Diffs - pom.xml b40fbcc5a Diff: https://reviews.apache.org/r/74760/diff/1/ Testing --- Passed junit tests. Verified policy and user crude operations. created keys in kms. Thanks, bhavik patel
[jira] [Updated] (RANGER-4563) Upgrade Jetty-client version to 9.4.53.v20231009
[ https://issues.apache.org/jira/browse/RANGER-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-4563: - Attachment: 0001-RANGER-4563-Upgrade-Jetty-client-version-to-9.4.53.v.patch > Upgrade Jetty-client version to 9.4.53.v20231009 > > > Key: RANGER-4563 > URL: https://issues.apache.org/jira/browse/RANGER-4563 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: > 0001-RANGER-4563-Upgrade-Jetty-client-version-to-9.4.53.v.patch > > > Upgrade Jetty-client version to 9.4.53.v20231009 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4563) Upgrade Jetty-client version to 9.4.53.v20231009
Bhavik Patel created RANGER-4563: Summary: Upgrade Jetty-client version to 9.4.53.v20231009 Key: RANGER-4563 URL: https://issues.apache.org/jira/browse/RANGER-4563 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade Jetty-client version to 9.4.53.v20231009 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (RANGER-4438) Read JAVA_OPTS in ranger db setup python script
[ https://issues.apache.org/jira/browse/RANGER-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reopened RANGER-4438: - > Read JAVA_OPTS in ranger db setup python script > --- > > Key: RANGER-4438 > URL: https://issues.apache.org/jira/browse/RANGER-4438 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4438.patch, RANGER-4438-2.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74755: RANGER-4558 : User is allowed to create/update sharedResource, even if the user is not zoneAdmin in the linked dataShared
> On Nov. 25, 2023, 8:17 a.m., Madhan Neethiraj wrote: > > > 5)Expected : The current user should be zoneAdmin as well as dataShare > > > Admin to create/upadate shared Resource > > > > Prashant - user with one of the following privileges should be allowed to > > create/update/delete shared-resources in a dataShare > > - Datashare admin > > - Zone admin > > - Service admin > > - Ranger admin Prashant - please ignore my earlier comment. Here is the requirement: 1. add/update shared resource: will require admin privilege on **both** dataShare and one of zone/service/Ranger 2. remove a shared resource: will require admin privilege on **either** dataShare or one of zone/service/Ranger Please make sure this patch addressed both #1 and #2. Thanks! - Madhan --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74755/#review226001 --- On Nov. 24, 2023, 11:14 a.m., Prashant Satam wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74755/ > --- > > (Updated Nov. 24, 2023, 11:14 a.m.) > > > Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, > Monika Kachhadiya, Subhrat Chaudhary, and Vanita Ubale. > > > Bugs: RANGER-4558 > https://issues.apache.org/jira/browse/RANGER-4558 > > > Repository: ranger > > > Description > --- > > User should be zoneAdmin along with datashare admin of linked sharedResource > to create/update > > Steps to check >1)Create SecurityZone >2)Create dataShare link SecurityZone to it >3)Current user is only zoneAdmin not datashare admin >4)Current User is able to create/upadate shared Resource >5)Expected : The current user should be zoneAdmin as well as dataShare > Admin to create/upadate shared Resource > > > Diffs > - > > > security-admin/src/main/java/org/apache/ranger/validation/RangerGdsValidator.java > d0a1142f6 > > > Diff: https://reviews.apache.org/r/74755/diff/1/ > > > Testing > --- > > Steps to Check > 1)Create SecurityZone > 2)Create dataShare link SecurityZone to it > 3)Current user is zoneAdmin and datashare admin > 4)Current User is able to create/upadate shared Resource > > > Thanks, > > Prashant Satam > >
[jira] [Commented] (RANGER-4559) Migrate Ranger modules to junit5 - phase 1
[ https://issues.apache.org/jira/browse/RANGER-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789802#comment-17789802 ] Kishor Gollapalliwar commented on RANGER-4559: -- RR: https://reviews.apache.org/r/74756/ > Migrate Ranger modules to junit5 - phase 1 > -- > > Key: RANGER-4559 > URL: https://issues.apache.org/jira/browse/RANGER-4559 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > This sub-task is responsible to migrate following maven sub-modules to junit5. > # conditions-enrichers > # credentialsbuilder > # embeddedwebserver > # jisql > # ldapconfigcheck > # ranger-atlas-plugin > # ranger-atlas-plugin-shim > # ranger-authn > # ranger-common-ha > # ranger-elasticsearch-plugin > # ranger-elasticsearch-plugin-shim > # ranger-hive-plugin > # ranger-hive-plugin-shim > # ranger-intg > # ranger-kafka-plugin > # ranger-kafka-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
