[jira] [Comment Edited] (RANGER-4478) Incorrect trie updates when processing deltas

2023-10-23 Thread Abhay Kulkarni (Jira) 


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

Abhay Kulkarni edited comment on RANGER-4478 at 10/23/23 10:50 PM:
---

Commit details:

master:

[https://github.com/apache/ranger/commit/0e7d63022252dc3c74478aa32bffac3ea755fee9]

 

[https://github.com/apache/ranger/commit/36ce62eabbcc38112b15e376411fb053ef8d2ed9]

 


was (Author: abhayk):
Commit details:

master:

https://github.com/apache/ranger/commit/0e7d63022252dc3c74478aa32bffac3ea755fee9

> Incorrect trie updates when processing deltas
> -
>
> Key: RANGER-4478
> URL: https://issues.apache.org/jira/browse/RANGER-4478
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Major
>
> When a plugin is configured to receive policy-deltas, policy engine 
> processing of the deltas to update its resource tries can result some 
> policies to be not included in the trie.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74694: RANGER-4478: Incorrect trie updates when processing deltas - Part 2

2023-10-23 Thread Madhan Neethiraj 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74694/#review225889
---


Ship it!




Ship It!

- Madhan Neethiraj


On Oct. 23, 2023, 8:23 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74694/
> ---
> 
> (Updated Oct. 23, 2023, 8:23 p.m.)
> 
> 
> Review request for ranger, madhan and Madhan Neethiraj.
> 
> 
> Bugs: RANGER-4478
> https://issues.apache.org/jira/browse/RANGER-4478
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> This is a follow-up patch for RANGER-4478 
> (https://reviews.apache.org/r/74680/). This patch removes calls to 
> undoSetup() during modification of the Trie object because, when the Trie 
> object was copied from the Trie object for earlier version of policies/tags, 
> the undoSetup() is called and calling it again will be unnecessary at best.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
>  61b6a4357 
> 
> 
> Diff: https://reviews.apache.org/r/74694/diff/1/
> 
> 
> Testing
> ---
> 
> Compiled and ran unit tests successfully.
> 
> Tested with a long running cluster with a client updating Hive policies 
> frequenty and Hive queries issued from a beeline client.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

[jira] [Comment Edited] (RANGER-4478) Incorrect trie updates when processing deltas

2023-10-23 Thread Abhay Kulkarni (Jira) 


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

Abhay Kulkarni edited comment on RANGER-4478 at 10/23/23 8:24 PM:
--

Patch is available here - [https://reviews.apache.org/r/74680/]

 

Follow-up patch is available here -https://reviews.apache.org/r/74694/


was (Author: abhayk):
Patch is available here - https://reviews.apache.org/r/74680/

> Incorrect trie updates when processing deltas
> -
>
> Key: RANGER-4478
> URL: https://issues.apache.org/jira/browse/RANGER-4478
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Major
>
> When a plugin is configured to receive policy-deltas, policy engine 
> processing of the deltas to update its resource tries can result some 
> policies to be not included in the trie.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Review Request 74694: RANGER-4478: Incorrect trie updates when processing deltas - Part 2

2023-10-23 Thread Abhay Kulkarni 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74694/
---

Review request for ranger, madhan and Madhan Neethiraj.


Bugs: RANGER-4478
https://issues.apache.org/jira/browse/RANGER-4478


Repository: ranger


Description
---

This is a follow-up patch for RANGER-4478 
(https://reviews.apache.org/r/74680/). This patch removes calls to undoSetup() 
during modification of the Trie object because, when the Trie object was copied 
from the Trie object for earlier version of policies/tags, the undoSetup() is 
called and calling it again will be unnecessary at best.


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceTrie.java
 61b6a4357 


Diff: https://reviews.apache.org/r/74694/diff/1/


Testing
---

Compiled and ran unit tests successfully.

Tested with a long running cluster with a client updating Hive policies 
frequenty and Hive queries issued from a beeline client.


Thanks,

Abhay Kulkarni

Re: Review Request 74690: RANGER-4266: gds info retrieval by plugins

2023-10-23 Thread Madhan Neethiraj 


> On Oct. 23, 2023, 6:31 a.m., Subhrat Chaudhary wrote:
> > agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceGdsInfo.java
> > Lines 218 (patched)
> > 
> >
> > Do we need SharedResourceInfo here?

Good point. I updated ServiceGdsInfo to make is easier to deal with delta 
updates.


- Madhan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74690/#review225885
---


On Oct. 23, 2023, 3:06 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74690/
> ---
> 
> (Updated Oct. 23, 2023, 3:06 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Abhay Kulkarni, Monika Kachhadiya, 
> Prashant Satam, Ramesh Mani, Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4266
> https://issues.apache.org/jira/browse/RANGER-4266
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> - REST API for plugins to download GDS info, similar to policies, tags, 
> userstore
> - Ranger updates to increment gdsVersion in services 
> - updated plugins library to implicitly add GDS enricher
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/admin/client/AbstractRangerAdminClient.java
>  a65c18708 
>   
> agents-common/src/main/java/org/apache/ranger/admin/client/RangerAdminClient.java
>  22a8121ca 
>   
> agents-common/src/main/java/org/apache/ranger/admin/client/RangerAdminRESTClient.java
>  9cd0fd263 
>   
> agents-common/src/main/java/org/apache/ranger/authorization/hadoop/config/RangerPluginConfig.java
>  df6307eb2 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerAdminGdsInfoRetriever.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerGdsEnricher.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerGdsInfoRetriever.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPolicyDelta.java
>  6eae590c4 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
>  2f4af9763 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/JsonUtilsV2.java 
> 9a8546b79 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTUtils.java
>  b265e8575 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceDefUtil.java 
> 489476b28 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceGdsInfo.java 
> PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/ServicePolicies.java
>  225f8526b 
>   security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 
> 19ecc1fc8 
>   security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
> ea98736a1 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> 10986823d 
>   security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java 
> 055c31364 
>   security-admin/src/main/java/org/apache/ranger/db/XXGdsDataShareDao.java 
> f0e64d711 
>   security-admin/src/main/java/org/apache/ranger/db/XXGdsDatasetDao.java 
> ee2d4b67b 
>   security-admin/src/main/java/org/apache/ranger/db/XXGdsProjectDao.java 
> 4f214ff8d 
>   security-admin/src/main/java/org/apache/ranger/db/XXServiceDao.java 
> c0f9d5c4e 
>   
> security-admin/src/main/java/org/apache/ranger/entity/XXServiceVersionInfo.java
>  04f030b35 
>   security-admin/src/main/java/org/apache/ranger/rest/GdsREST.java 4c0a106ad 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsBaseModelService.java
>  e7c54385f 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareInDatasetService.java
>  569509d66 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareService.java
>  6a93e44dc 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetInProjectService.java
>  d62040175 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetService.java
>  75833ea7b 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsProjectService.java
>  4ccb063fe 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsSharedResourceService.java
>  4bdb09f4d 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerServiceService.java
>  9bf7868d0 
>   security-admin/src/main/resources/META-INF/jpa_named_queries.xml 547913488 
>   security-admin/src/main/resources/conf.dist/security-applicationContext.xml 
> 807791f28 
>   security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBStore.java 
> eadd64ab7 
>

Re: Review Request 74690: RANGER-4266: gds info retrieval by plugins

2023-10-23 Thread Madhan Neethiraj 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74690/
---

(Updated Oct. 23, 2023, 3:06 p.m.)


Review request for ranger, Ankita Sinha, Abhay Kulkarni, Monika Kachhadiya, 
Prashant Satam, Ramesh Mani, Subhrat Chaudhary, and Velmurugan Periasamy.


Changes
---

addressed review comments


Bugs: RANGER-4266
https://issues.apache.org/jira/browse/RANGER-4266


Repository: ranger


Description
---

- REST API for plugins to download GDS info, similar to policies, tags, 
userstore
- Ranger updates to increment gdsVersion in services 
- updated plugins library to implicitly add GDS enricher


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/admin/client/AbstractRangerAdminClient.java
 a65c18708 
  
agents-common/src/main/java/org/apache/ranger/admin/client/RangerAdminClient.java
 22a8121ca 
  
agents-common/src/main/java/org/apache/ranger/admin/client/RangerAdminRESTClient.java
 9cd0fd263 
  
agents-common/src/main/java/org/apache/ranger/authorization/hadoop/config/RangerPluginConfig.java
 df6307eb2 
  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerAdminGdsInfoRetriever.java
 PRE-CREATION 
  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerGdsEnricher.java
 PRE-CREATION 
  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerGdsInfoRetriever.java
 PRE-CREATION 
  
agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPolicyDelta.java
 6eae590c4 
  
agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
 2f4af9763 
  agents-common/src/main/java/org/apache/ranger/plugin/util/JsonUtilsV2.java 
9a8546b79 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTUtils.java 
b265e8575 
  agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceDefUtil.java 
489476b28 
  agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceGdsInfo.java 
PRE-CREATION 
  
agents-common/src/main/java/org/apache/ranger/plugin/util/ServicePolicies.java 
225f8526b 
  security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 19ecc1fc8 
  security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
ea98736a1 
  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 10986823d 
  security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java 
055c31364 
  security-admin/src/main/java/org/apache/ranger/db/XXGdsDataShareDao.java 
f0e64d711 
  security-admin/src/main/java/org/apache/ranger/db/XXGdsDatasetDao.java 
ee2d4b67b 
  security-admin/src/main/java/org/apache/ranger/db/XXGdsProjectDao.java 
4f214ff8d 
  security-admin/src/main/java/org/apache/ranger/db/XXServiceDao.java c0f9d5c4e 
  
security-admin/src/main/java/org/apache/ranger/entity/XXServiceVersionInfo.java 
04f030b35 
  security-admin/src/main/java/org/apache/ranger/rest/GdsREST.java 4c0a106ad 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsBaseModelService.java
 e7c54385f 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareInDatasetService.java
 569509d66 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareService.java
 6a93e44dc 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetInProjectService.java
 d62040175 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetService.java
 75833ea7b 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsProjectService.java
 4ccb063fe 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsSharedResourceService.java
 4bdb09f4d 
  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceService.java
 9bf7868d0 
  security-admin/src/main/resources/META-INF/jpa_named_queries.xml 547913488 
  security-admin/src/main/resources/conf.dist/security-applicationContext.xml 
807791f28 
  security-admin/src/test/java/org/apache/ranger/biz/TestServiceDBStore.java 
eadd64ab7 
  security-admin/src/test/java/org/apache/ranger/biz/TestTagDBStore.java 
10c3eb4bb 


Diff: https://reviews.apache.org/r/74690/diff/6/

Changes: https://reviews.apache.org/r/74690/diff/5-6/


Testing
---

- verified that the plugins successfully download GDS information


Thanks,

Madhan Neethiraj

[jira] [Updated] (RANGER-4492) Optimize "plugins/definitions" API Call for Initial Load in Multiple Ranger-React Modules

2023-10-23 Thread Mugdha Varadkar (Jira) 


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

Mugdha Varadkar updated RANGER-4492:

Description: 
In Ranger React, we have already implemented the "plugins/definitions" API call 
at the initial load for optimization. 

This optimization is currently implemented on the Service Manager page and 
needs to be extended to the following modules:
1)Audit
2)Report
3)Security Zone
4)Key Manager

This enhancement aims to improve the initial load performance by efficiently 
utilizing the "plugins/definitions" API call across multiple modules within 
Ranger-React.

  was:
Implement the "plugins/definitions" API call at the initial load for 
optimization in Ranger-React. 
This optimization is currently implemented on the Service Manager page and 
needs to be extended to the following modules:
1)Audit
2)Report
3)Security Zone
4)Key Manager

This enhancement aims to improve the initial load performance by efficiently 
utilizing the "plugins/definitions" API call across multiple modules within 
Ranger-React.


> Optimize "plugins/definitions" API Call for Initial Load in Multiple 
> Ranger-React Modules
> -
>
> Key: RANGER-4492
> URL: https://issues.apache.org/jira/browse/RANGER-4492
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
>
> In Ranger React, we have already implemented the "plugins/definitions" API 
> call at the initial load for optimization. 
> This optimization is currently implemented on the Service Manager page and 
> needs to be extended to the following modules:
> 1)Audit
> 2)Report
> 3)Security Zone
> 4)Key Manager
> This enhancement aims to improve the initial load performance by efficiently 
> utilizing the "plugins/definitions" API call across multiple modules within 
> Ranger-React.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74692: RANGER:4473:Dataset/Datashare/Shared-resource/project name should not be created with trailing spaces

2023-10-23 Thread Ankita Sinha 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74692/#review225887
---


Ship it!




Ship It!

- Ankita Sinha


On Oct. 23, 2023, 9:59 a.m., Prashant Satam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74692/
> ---
> 
> (Updated Oct. 23, 2023, 9:59 a.m.)
> 
> 
> Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, 
> Monika Kachhadiya, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4473
> https://issues.apache.org/jira/browse/RANGER-4473
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Dataset/Datashare/SharedResource/project names are being created with 
> trailing spaces which should not be happening since in the UI they will be 
> seen as duplicate with the same names.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> 10986823d 
> 
> 
> Diff: https://reviews.apache.org/r/74692/diff/2/
> 
> 
> Testing
> ---
> 
> 1)Create /Datashare/SharedResource/project with trailing spaces 
> 2)The response we receive after POST will not have trailing spaces for field 
> name
>  Example 
> Request ---> POST - service/gds/project
> 
> Response --> 
> {
> "id": 3,
> "guid": "7254a3b0-972a-4fe4-88af-b9fb591b812b",
> "isEnabled": true,
> "createdBy": "Admin",
> "updatedBy": "Admin",
> "createTime": 1698040479295,
> "updateTime": 1698040479295,
> "version": 1,
> "name": "Ranger-Project-1",
> "acl": {
> "users": {
> "admin": "ADMIN"
> }
> }
> }
> 
> 
> Thanks,
> 
> Prashant Satam
> 
>

[jira] [Updated] (RANGER-4490) Need new API for DataShare in Dataset Summary

2023-10-23 Thread Prashant Satam (Jira) 


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

Prashant Satam updated RANGER-4490:
---
Description: 
Get dataShareInDataset Summary objects with filters

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

linkedProjectId/linkedProjectName -> in case of datasets we need this query 
param to ensure we only get datasets that are connected to the given project 
AND also have dataShares linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

Details of the API --

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial

  was:
Get dataShareInDataset Summary objects with filters

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

linkedProjectId/linkedProjectName -> in case of datasets we need this query 
param to ensure we only get datasets that are connected to the given project 
AND also have dataShares linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

Details of the API 

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial


> Need new API for DataShare in Dataset Summary
> -
>
> Key: RANGER-4490
> URL: https://issues.apache.org/jira/browse/RANGER-4490
> Project: Ranger
>  Issue Type: Sub-task
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Get dataShareInDataset Summary objects with filters
> The API is required for "My Requests" page to show mapping of dataset with 
> datashare 
> Required Fields for the page are 
> (datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)
> Need to add new query params 
> linkedServiceId/linkedServiceName -> in case of dataShares we need 
> this query param to ensure we get only those dataShares that are linked to 
> the given service AND also have datasets linked to them 
> linkedZoneId/linkedZoneName -> in case of dataShares we need this 
> query param to ensure we get only

Re: Review Request 74681: RANGER:4480:Disable pagination for GDS APIs

2023-10-23 Thread Prashant Satam 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74681/
---

(Updated Oct. 23, 2023, 11:41 a.m.)


Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, Monika 
Kachhadiya, and Subhrat Chaudhary.


Bugs: RANGER-4480
https://issues.apache.org/jira/browse/RANGER-4480


Repository: ranger


Description (updated)
---

In case of GDS we cannot apply pagination from DB side Directly as some filters 
are after the DB results with pagination enabled (i.e without 
pageSize,startIndex as query params)we get result in batch size of 200 (default 
pageSize) then this result is incomplete to apply filters which are after the 
DB result (i.e filters which are in code only) 

Example 

1)GET shared resource API we have a query param 'resourceContains' using this 
we can get shared-resource which has resource value matching with the query 
param

Problem is if we have more than 200 shared resources (i.e beyond default 
pageSize) in DB and we pass this param and the actual object resides in DB 
beyond the pageSize limit and we dont have pageSize,startIndex in the request 
then we will only retrive from DB only 200 shared-resources and further filters 
will only get applied on those 200 objects but we did not retrive the actual 
object we expect at response as it was beyond the default pageSize 

So in case of GDS APIs we need to disable pagination


Diffs
-

  agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
93bd7f73d 
  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 10986823d 
  security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
719d8a900 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareService.java
 6a93e44dc 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetService.java
 072889f1d 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsProjectService.java
 4ccb063fe 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsSharedResourceService.java
 4bdb09f4d 


Diff: https://reviews.apache.org/r/74681/diff/1/


Testing
---

1)Create shared resources more than default pageSize i.e 200
2)use GET-API > (/service/gds/resource) to fetch resource which has 
resourceContains = resource_1 this shared resource should be beyond the 
pageSize 200 
3)In response you will receive the shared resource having resource as 
resource_1 which was beyond 200th position in DB
Request -> (/service/gds/resource?resourceContains=resource_1)
Response->
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 1,
"resultSize": 1,
"sortType": "sharedResourceId",
"sortBy": "asc",
"queryTimeMS": 1697626402403,
"list": [
{
"id": 388,
"guid": "1d9e2fcf-8cc8-45b0-ab87-3f596c04350a",
"isEnabled": true,
"createdBy": "Admin",
"updatedBy": "Admin",
"createTime": 1697192628000,
"updateTime": 1697192628000,
"version": 1,
"description": "This is RangerResource",
"options": {
"property1": "This is Options 1",
"property2": "This is Options 2"
},
"additionalInfo": {
"property1": "This is AdditionalInfo 1",
"property2": "This is AdditionalInfo 2"
},
"name": "RangerResource_399",
"dataShareId": 1,
"resource": {
"RAngerResourceName": {
"values": [
"res_399",
"res_399"
],
"isExcludes": true,
"isRecursive": true
}
},
"conditionExpr": "conditionExpr_1",
"accessTypes": [
"Resource_Access_type_1",
"Resource_Access_type_2"
],
"profiles": [
"resource_profile_1",
"resource_profile_2"
]
}
],
"listSize": 1
}


Thanks,

Prashant Satam

[jira] [Updated] (RANGER-4480) Disable pagination for GDS APIs

2023-10-23 Thread Prashant Satam (Jira) 


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

Prashant Satam updated RANGER-4480:
---
Description: 
In case of GDS we cannot apply pagination from DB side Directly as some filters 
are after the DB results with pagination enabled (i.e without 
pageSize,startIndex as query params)we get result in batch size of 200 (default 
pageSize) then this result is incomplete to apply filters which are after the 
DB result (i.e filters which are in code only) 

Example 

1)GET shared resource API we have a query param 'resourceContains' using this 
we can get shared-resource which has resource value matching with the query 
param

Problem is if we have more than 200 shared resources (i.e beyond default 
pageSize) in DB and we pass this param and the actual object resides in DB 
beyond the pageSize limit and we dont have pageSize,startIndex in the request 
then we will only retrive from DB only 200 shared-resources and further filters 
will only get applied on those 200 objects but we did not retrive the actual 
object we expect at response as it was beyond the default pageSize 

So in case of GDS APIs we need to disable pagination

  was:In case of GDS we cannot apply pagination from DB side Directly as some 
filters are after the DB results with pagination enabled we get result in batch 
size of 200 then this result is incomplete to apply filters which are after the 
DB result (i.e filters which are in code only) 


> Disable pagination for GDS APIs
> ---
>
> Key: RANGER-4480
> URL: https://issues.apache.org/jira/browse/RANGER-4480
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> In case of GDS we cannot apply pagination from DB side Directly as some 
> filters are after the DB results with pagination enabled (i.e without 
> pageSize,startIndex as query params)we get result in batch size of 200 
> (default pageSize) then this result is incomplete to apply filters which are 
> after the DB result (i.e filters which are in code only) 
> Example 
> 1)GET shared resource API we have a query param 'resourceContains' using this 
> we can get shared-resource which has resource value matching with the query 
> param
> Problem is if we have more than 200 shared resources (i.e beyond default 
> pageSize) in DB and we pass this param and the actual object resides in DB 
> beyond the pageSize limit and we dont have pageSize,startIndex in the request 
> then we will only retrive from DB only 200 shared-resources and further 
> filters will only get applied on those 200 objects but we did not retrive the 
> actual object we expect at response as it was beyond the default pageSize 
> So in case of GDS APIs we need to disable pagination



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74688: RANGER:4490:Need new API for DataShare in Dataset Summary

2023-10-23 Thread Prashant Satam 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74688/
---

(Updated Oct. 23, 2023, 11:26 a.m.)


Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, Monika 
Kachhadiya, and Subhrat Chaudhary.


Bugs: RANGER-4490
https://issues.apache.org/jira/browse/RANGER-4490


Repository: ranger


Description (updated)
---

Get dataShareInDataset Summary objects with filters

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

linkedProjectId/linkedProjectName -> in case of datasets we need this query 
param to ensure we only get datasets that are connected to the given project 
AND also have dataShares linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

Details of the API 

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial


Need to merge after (https://reviews.apache.org/r/74681/)


Diffs
-

  agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
93bd7f73d 
  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 10986823d 
  security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
f8b7837c5 
  security-admin/src/main/java/org/apache/ranger/rest/GdsREST.java 4c0a106ad 
  
security-admin/src/main/java/org/apache/ranger/security/context/RangerAPIList.java
 f21d445c4 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareInDatasetService.java
 569509d66 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareService.java
 6a93e44dc 
  
security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetService.java
 75833ea7b 


Diff: https://reviews.apache.org/r/74688/diff/2/


Testing
---

1)Create a dataset
2)Create a dataShare (create service,create security-zone attach them to the 
dataShare while creating)
3)Create a project (attach created dataset with project)
4)Link dataset with dataShare

use GET-API --> (/service/gds/datashare/dataset/summary) will get 
objects of dataset-in-datashare-summary

Supported Query Params
1)linkedServiceId,linkedServiceName,linkedServiceNamePartial > will 
get objList based on service linked to datashares
2)linkedZoneId,linkedZoneName,linkedZoneNamePartial ---> will get 
objList based on security-zone linked to datashares
3)linkedProjectId,linkedProjectName,linkedProjectNamePartial > will 
get objList based on project linked to dataset

Request  -> (/service/gds/datashare/dataset/summary?linkedZoneId=)
Response --> 
{
"startIndex": 0,
"pageSize": 200,
"totalCount": 1,
"resultSize": 1,
"sortType": "dataShareInDatasetId",
"sortBy": "ASC",
"queryTimeMS": 1697803539620,
"list": [
{
"id": 2,
"guid": "64ef719b-38ca-442c-a246-3bf6bf7afead",
"isEnabled": true,
"createdBy": "Admin",
"updatedBy": "Admin",
"createTime": 169771366,
"updateTime": 169771366,
"datasetId": 1,
"datasetName": "Test_GDS_Dataset82",
"dataShareId": 2,
"dataShareName": "RangerDataShare61",
"serviceId": 1,
"serviceName": "Ranger_hive",
"zoneId": 2,
"zoneName": "test-Zone-1",
"resourceCount": 0,
"shareStatus": "NONE",
"approver":"admin"
}
],
"listSize": 1
}


Thanks,

Prashant

[jira] [Updated] (RANGER-4490) Need new API for DataShare in Dataset Summary

2023-10-23 Thread Prashant Satam (Jira) 


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

Prashant Satam updated RANGER-4490:
---
Description: 
Get dataShareInDataset Summary objects with filters

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

linkedProjectId/linkedProjectName -> in case of datasets we need this query 
param to ensure we only get datasets that are connected to the given project 
AND also have dataShares linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

Details of the API 

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial

  was:
Get dataShareInDataset Summary objects with filters

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

Details of the API 

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial


> Need new API for DataShare in Dataset Summary
> -
>
> Key: RANGER-4490
> URL: https://issues.apache.org/jira/browse/RANGER-4490
> Project: Ranger
>  Issue Type: Sub-task
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Get dataShareInDataset Summary objects with filters
> The API is required for "My Requests" page to show mapping of dataset with 
> datashare 
> Required Fields for the page are 
> (datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)
> Need to add new query params 
> linkedServiceId/linkedServiceName -> in case of dataShares we need 
> this query param to ensure we get only those dataShares that are linked to 
> the given service AND also have datasets linked to them 
> linkedZoneId/linkedZoneName -> in case of dataShares we need this 
> query param to ensure we get only those dataShares that are linked to the 
> given security-zone AND also have datasets linked to them 
> linkedProjectId/linkedProjectName -> in case of datasets we need this 
> query param to ensure we only get datasets that are connected to

[jira] [Updated] (RANGER-4490) Need new API for DataShare in Dataset Summary

2023-10-23 Thread Prashant Satam (Jira) 


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

Prashant Satam updated RANGER-4490:
---
Description: 
Get dataShareInDataset Summary objects with filters

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

Details of the API 

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial

  was:
Get dataShareInDataset Summary objects with

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

Details of the API 

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial


> Need new API for DataShare in Dataset Summary
> -
>
> Key: RANGER-4490
> URL: https://issues.apache.org/jira/browse/RANGER-4490
> Project: Ranger
>  Issue Type: Sub-task
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Get dataShareInDataset Summary objects with filters
> The API is required for "My Requests" page to show mapping of dataset with 
> datashare 
> Required Fields for the page are 
> (datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)
> Need to add new query params 
> linkedServiceId/linkedServiceName -> in case of dataShares we need 
> this query param to ensure we get only those dataShares that are linked to 
> the given service AND also have datasets linked to them 
> linkedZoneId/linkedZoneName -> in case of dataShares we need this 
> query param to ensure we get only those dataShares that are linked to the 
> given security-zone AND also have datasets linked to them 
> In case of dataShares the Existing query Params like serviceId/serviceName  
> only return dataShares connected to the service but this do not ensure that 
> the same dataShare is connected to any dataset 
> Also for query param zoneId/zoneName from dataShare side only return 
> dataShares connected to the given security-zone but this do not ensure

[jira] [Updated] (RANGER-4490) Need new API for DataShare in Dataset Summary

2023-10-23 Thread Prashant Satam (Jira) 


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

Prashant Satam updated RANGER-4490:
---
Description: 
Get dataShareInDataset Summary objects with

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

Details of the API 

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial

  was:
Get dataShareInDataset Summary objects with

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial


> Need new API for DataShare in Dataset Summary
> -
>
> Key: RANGER-4490
> URL: https://issues.apache.org/jira/browse/RANGER-4490
> Project: Ranger
>  Issue Type: Sub-task
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Get dataShareInDataset Summary objects with
> The API is required for "My Requests" page to show mapping of dataset with 
> datashare 
> Required Fields for the page are 
> (datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)
> Need to add new query params 
> linkedServiceId/linkedServiceName -> in case of dataShares we need 
> this query param to ensure we get only those dataShares that are linked to 
> the given service AND also have datasets linked to them 
> linkedZoneId/linkedZoneName -> in case of dataShares we need this 
> query param to ensure we get only those dataShares that are linked to the 
> given security-zone AND also have datasets linked to them 
> In case of dataShares the Existing query Params like serviceId/serviceName  
> only return dataShares connected to the service but this do not ensure that 
> the same dataShare is connected to any dataset 
> Also for query param zoneId/zoneName from dataShare side only return 
> dataShares connected to the given security-zone but this do not ensure that 
> the same dataShare is

[jira] [Updated] (RANGER-4490) Need new API for DataShare in Dataset Summary

2023-10-23 Thread Prashant Satam (Jira) 


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

Prashant Satam updated RANGER-4490:
---
Description: 
Get dataShareInDataset Summary objects with

The API is required for "My Requests" page to show mapping of dataset with 
datashare 

Required Fields for the page are 
(datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)

Need to add new query params 

linkedServiceId/linkedServiceName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
service AND also have datasets linked to them 

linkedZoneId/linkedZoneName -> in case of dataShares we need this 
query param to ensure we get only those dataShares that are linked to the given 
security-zone AND also have datasets linked to them 

In case of dataShares the Existing query Params like serviceId/serviceName  
only return dataShares connected to the service but this do not ensure that the 
same dataShare is connected to any dataset 

Also for query param zoneId/zoneName from dataShare side only return dataShares 
connected to the given security-zone but this do not ensure that the same 
dataShare is connected to any dataset

in case of dataset the Existing param projectId/projectName will only return 
the datasets connected to the project but this do not ensure that the dataset 
is connected to any dataShare

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial

  was:
Get dataShareInDataset Summary objects with

FIELDS 
(datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
 on dataShare),zoneName,shareStatus,)

Supported Query Params

linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial


> Need new API for DataShare in Dataset Summary
> -
>
> Key: RANGER-4490
> URL: https://issues.apache.org/jira/browse/RANGER-4490
> Project: Ranger
>  Issue Type: Sub-task
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Get dataShareInDataset Summary objects with
> The API is required for "My Requests" page to show mapping of dataset with 
> datashare 
> Required Fields for the page are 
> (datasetName,dataShareName,sharedStatus,createTime,updateTime,createdBy)
> Need to add new query params 
> linkedServiceId/linkedServiceName -> in case of dataShares we need 
> this query param to ensure we get only those dataShares that are linked to 
> the given service AND also have datasets linked to them 
> linkedZoneId/linkedZoneName -> in case of dataShares we need this 
> query param to ensure we get only those dataShares that are linked to the 
> given security-zone AND also have datasets linked to them 
> In case of dataShares the Existing query Params like serviceId/serviceName  
> only return dataShares connected to the service but this do not ensure that 
> the same dataShare is connected to any dataset 
> Also for query param zoneId/zoneName from dataShare side only return 
> dataShares connected to the given security-zone but this do not ensure that 
> the same dataShare is connected to any dataset
> in case of dataset the Existing param projectId/projectName will only return 
> the datasets connected to the project but this do not ensure that the dataset 
> is connected to any dataShare
> FIELDS 
> (datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based
>  on dataShare),zoneName,shareStatus,)
> Supported Query Params
> linkedServiceId,linkedServiceName,linkedServiceNamePartial,linkedZoneId,linkedZoneName,linkedZoneNamePartial,linkedProjectId,linkedProjectName,linkedProjectNamePartial



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4434) Need a new API to get list of requests for the current user

2023-10-23 Thread Subhrat Chaudhary (Jira) 


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

Subhrat Chaudhary commented on RANGER-4434:
---

Duplicate of https://issues.apache.org/jira/browse/RANGER-4434

> Need a new API to get list of requests for the current user
> ---
>
> Key: RANGER-4434
> URL: https://issues.apache.org/jira/browse/RANGER-4434
> Project: Ranger
>  Issue Type: Sub-task
>  Components: admin
>Reporter: Subhrat Chaudhary
>Priority: Major
>
> Need a new API to get list of requests for the current user for the My 
> Requests page



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Resolved] (RANGER-4434) Need a new API to get list of requests for the current user

2023-10-23 Thread Subhrat Chaudhary (Jira) 


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

Subhrat Chaudhary resolved RANGER-4434.
---
Resolution: Duplicate

> Need a new API to get list of requests for the current user
> ---
>
> Key: RANGER-4434
> URL: https://issues.apache.org/jira/browse/RANGER-4434
> Project: Ranger
>  Issue Type: Sub-task
>  Components: admin
>Reporter: Subhrat Chaudhary
>Priority: Major
>
> Need a new API to get list of requests for the current user for the My 
> Requests page



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Review Request 74693: RANGER:4417:Add default policy for new dataset

2023-10-23 Thread Prashant Satam 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74693/
---

Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, Monika 
Kachhadiya, and Subhrat Chaudhary.


Bugs: RANGER-4417
https://issues.apache.org/jira/browse/RANGER-4417


Repository: ranger


Description
---

When a dataset is created, a default policy should also be created for same 
implicitly.


Diffs
-

  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 10986823d 


Diff: https://reviews.apache.org/r/74693/diff/1/


Testing
---

1)Create a dataset by POST API > service/gds/dataset
2)You will get policy for the same dataset i.e default policy 
Example for default policy --->
{
"id": 36,
"guid": "69a94aad-e866-4b16-9918-acbc9a82a321",
"isEnabled": true,
"createdBy": "Admin",
"updatedBy": "Admin",
"createTime": 1698054263086,
"updateTime": 1698054263095,
"version": 1,
"service": "_gds",
"name": "DATASET: Test_GDS_Dataset92@1698054263081",
"policyType": 0,
"policyPriority": 0,
"description": "Policy for dataset: Test_GDS_Dataset92",
"resourceSignature": 
"e8dfb82306b597b69a046d3a9c9a56b9aa864172eb6f953e6ee87ff41db4b531",
"isAuditEnabled": true,
"resources": {
"dataset-id": {
"values": [
"6"
],
"isExcludes": false,
"isRecursive": false
}
},
"serviceType": "gds",
"isDenyAllElse": false
}


Thanks,

Prashant Satam

[jira] [Assigned] (RANGER-4417) Add default policy for new dataset

2023-10-23 Thread Prashant Satam (Jira) 


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

Prashant Satam reassigned RANGER-4417:
--

Assignee: Prashant Satam

> Add default policy for new dataset
> --
>
> Key: RANGER-4417
> URL: https://issues.apache.org/jira/browse/RANGER-4417
> Project: Ranger
>  Issue Type: Sub-task
>  Components: admin
>Reporter: Subhrat Chaudhary
>Assignee: Prashant Satam
>Priority: Major
>
> When a dataset is created, a default policy should also be created for same 
> implicitly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74692: RANGER:4473:Dataset/Datashare/Shared-resource/project name should not be created with trailing spaces

2023-10-23 Thread Prashant Satam 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74692/
---

(Updated Oct. 23, 2023, 9:59 a.m.)


Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, Monika 
Kachhadiya, and Subhrat Chaudhary.


Bugs: RANGER-4473
https://issues.apache.org/jira/browse/RANGER-4473


Repository: ranger


Description
---

Dataset/Datashare/SharedResource/project names are being created with trailing 
spaces which should not be happening since in the UI they will be seen as 
duplicate with the same names.


Diffs (updated)
-

  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 10986823d 


Diff: https://reviews.apache.org/r/74692/diff/2/

Changes: https://reviews.apache.org/r/74692/diff/1-2/


Testing
---

1)Create /Datashare/SharedResource/project with trailing spaces 
2)The response we receive after POST will not have trailing spaces for field 
name
 Example 
Request ---> POST - service/gds/project

Response --> 
{
"id": 3,
"guid": "7254a3b0-972a-4fe4-88af-b9fb591b812b",
"isEnabled": true,
"createdBy": "Admin",
"updatedBy": "Admin",
"createTime": 1698040479295,
"updateTime": 1698040479295,
"version": 1,
"name": "Ranger-Project-1",
"acl": {
"users": {
"admin": "ADMIN"
}
}
}


Thanks,

Prashant Satam

[jira] [Updated] (RANGER-4492) Optimize "plugins/definitions" API Call for Initial Load in Multiple Ranger-React Modules

2023-10-23 Thread Brijesh Bhalala (Jira) 


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

Brijesh Bhalala updated RANGER-4492:

Labels: ranger-react  (was: )

> Optimize "plugins/definitions" API Call for Initial Load in Multiple 
> Ranger-React Modules
> -
>
> Key: RANGER-4492
> URL: https://issues.apache.org/jira/browse/RANGER-4492
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
>
> Implement the "plugins/definitions" API call at the initial load for 
> optimization in Ranger-React. 
> This optimization is currently implemented on the Service Manager page and 
> needs to be extended to the following modules:
> 1)Audit
> 2)Report
> 3)Security Zone
> 4)Key Manager
> This enhancement aims to improve the initial load performance by efficiently 
> utilizing the "plugins/definitions" API call across multiple modules within 
> Ranger-React.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-4492) Optimize "plugins/definitions" API Call for Initial Load in Multiple Ranger-React Modules

2023-10-23 Thread Brijesh Bhalala (Jira) 


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

Brijesh Bhalala updated RANGER-4492:

Fix Version/s: 3.0.0

> Optimize "plugins/definitions" API Call for Initial Load in Multiple 
> Ranger-React Modules
> -
>
> Key: RANGER-4492
> URL: https://issues.apache.org/jira/browse/RANGER-4492
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
> Fix For: 3.0.0
>
>
> Implement the "plugins/definitions" API call at the initial load for 
> optimization in Ranger-React. 
> This optimization is currently implemented on the Service Manager page and 
> needs to be extended to the following modules:
> 1)Audit
> 2)Report
> 3)Security Zone
> 4)Key Manager
> This enhancement aims to improve the initial load performance by efficiently 
> utilizing the "plugins/definitions" API call across multiple modules within 
> Ranger-React.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (RANGER-4492) Optimize "plugins/definitions" API Call for Initial Load in Multiple Ranger-React Modules

2023-10-23 Thread Brijesh Bhalala (Jira) 


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

Brijesh Bhalala reassigned RANGER-4492:
---

Assignee: Brijesh Bhalala

> Optimize "plugins/definitions" API Call for Initial Load in Multiple 
> Ranger-React Modules
> -
>
> Key: RANGER-4492
> URL: https://issues.apache.org/jira/browse/RANGER-4492
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>
> Implement the "plugins/definitions" API call at the initial load for 
> optimization in Ranger-React. 
> This optimization is currently implemented on the Service Manager page and 
> needs to be extended to the following modules:
> 1)Audit
> 2)Report
> 3)Security Zone
> 4)Key Manager
> This enhancement aims to improve the initial load performance by efficiently 
> utilizing the "plugins/definitions" API call across multiple modules within 
> Ranger-React.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4492) Optimize "plugins/definitions" API Call for Initial Load in Multiple Ranger-React Modules

2023-10-23 Thread Brijesh Bhalala (Jira) 
Brijesh Bhalala created RANGER-4492:
---

 Summary: Optimize "plugins/definitions" API Call for Initial Load 
in Multiple Ranger-React Modules
 Key: RANGER-4492
 URL: https://issues.apache.org/jira/browse/RANGER-4492
 Project: Ranger
  Issue Type: Improvement
  Components: Ranger
Reporter: Brijesh Bhalala


Implement the "plugins/definitions" API call at the initial load for 
optimization in Ranger-React. 
This optimization is currently implemented on the Service Manager page and 
needs to be extended to the following modules:
1)Audit
2)Report
3)Security Zone
4)Key Manager

This enhancement aims to improve the initial load performance by efficiently 
utilizing the "plugins/definitions" API call across multiple modules within 
Ranger-React.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74690: RANGER-4266: gds info retrieval by plugins

2023-10-23 Thread Subhrat Chaudhary via Review Board 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74690/#review225885
---




agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerGdsEnricher.java
Lines 353 (patched)


There is an extra semicolon(;) here.



agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceGdsInfo.java
Lines 218 (patched)


Do we need SharedResourceInfo here?


- Subhrat Chaudhary


On Oct. 21, 2023, 2:16 p.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74690/
> ---
> 
> (Updated Oct. 21, 2023, 2:16 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Abhay Kulkarni, Monika Kachhadiya, 
> Prashant Satam, Ramesh Mani, Subhrat Chaudhary, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4266
> https://issues.apache.org/jira/browse/RANGER-4266
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> - REST API for plugins to download GDS info, similar to policies, tags, 
> userstore
> - Ranger updates to increment gdsVersion in services 
> - updated plugins library to implicitly add GDS enricher
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/admin/client/AbstractRangerAdminClient.java
>  a65c18708 
>   
> agents-common/src/main/java/org/apache/ranger/admin/client/RangerAdminClient.java
>  22a8121ca 
>   
> agents-common/src/main/java/org/apache/ranger/admin/client/RangerAdminRESTClient.java
>  9cd0fd263 
>   
> agents-common/src/main/java/org/apache/ranger/authorization/hadoop/config/RangerPluginConfig.java
>  df6307eb2 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerAdminGdsInfoRetriever.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerGdsEnricher.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerGdsInfoRetriever.java
>  PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPolicyDelta.java
>  6eae590c4 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java
>  2f4af9763 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/JsonUtilsV2.java 
> 9a8546b79 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTUtils.java
>  b265e8575 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceDefUtil.java 
> 489476b28 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceGdsInfo.java 
> PRE-CREATION 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/util/ServicePolicies.java
>  225f8526b 
>   security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 
> 19ecc1fc8 
>   security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
> ea98736a1 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> 10986823d 
>   security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java 
> 055c31364 
>   security-admin/src/main/java/org/apache/ranger/db/XXGdsDataShareDao.java 
> f0e64d711 
>   security-admin/src/main/java/org/apache/ranger/db/XXGdsDatasetDao.java 
> ee2d4b67b 
>   security-admin/src/main/java/org/apache/ranger/db/XXGdsProjectDao.java 
> 4f214ff8d 
>   security-admin/src/main/java/org/apache/ranger/db/XXServiceDao.java 
> c0f9d5c4e 
>   
> security-admin/src/main/java/org/apache/ranger/entity/XXServiceVersionInfo.java
>  04f030b35 
>   security-admin/src/main/java/org/apache/ranger/rest/GdsREST.java 4c0a106ad 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsBaseModelService.java
>  e7c54385f 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareInDatasetService.java
>  569509d66 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareService.java
>  6a93e44dc 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetInProjectService.java
>  d62040175 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetService.java
>  75833ea7b 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsProjectService.java
>  4ccb063fe 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsSharedResourceService.java
>  4bdb09f4d 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerServiceService.java
>  9bf7868d0 
>   security-admin/src/main/resources/META-INF/jpa_named_queries.xml 547913488 
>   security-admin/src/main/resources/conf.dist/security-applicationContext.xml 
> 807791f28 
>

Re: Review Request 74692: RANGER:4473:Dataset/Datashare/Shared-resource/project name should not be created with trailing spaces

2023-10-23 Thread Madhan Neethiraj 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74692/#review225886
---




security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java
Lines 184 (patched)


Consider the following, which is simpler:
  dataset.setName(StringUtils.trim(dataset.getName()));


- Madhan Neethiraj


On Oct. 23, 2023, 6:01 a.m., Prashant Satam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74692/
> ---
> 
> (Updated Oct. 23, 2023, 6:01 a.m.)
> 
> 
> Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, 
> Monika Kachhadiya, and Subhrat Chaudhary.
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Dataset/Datashare/SharedResource/project names are being created with 
> trailing spaces which should not be happening since in the UI they will be 
> seen as duplicate with the same names.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> 10986823d 
> 
> 
> Diff: https://reviews.apache.org/r/74692/diff/1/
> 
> 
> Testing
> ---
> 
> 1)Create /Datashare/SharedResource/project with trailing spaces 
> 2)The response we receive after POST will not have trailing spaces for field 
> name
>  Example 
> Request ---> POST - service/gds/project
> 
> Response --> 
> {
> "id": 3,
> "guid": "7254a3b0-972a-4fe4-88af-b9fb591b812b",
> "isEnabled": true,
> "createdBy": "Admin",
> "updatedBy": "Admin",
> "createTime": 1698040479295,
> "updateTime": 1698040479295,
> "version": 1,
> "name": "Ranger-Project-1",
> "acl": {
> "users": {
> "admin": "ADMIN"
> }
> }
> }
> 
> 
> Thanks,
> 
> Prashant Satam
> 
>

[jira] [Assigned] (RANGER-4427) Need a new API to get list of datasets for a datashare with request status

2023-10-23 Thread Prashant Satam (Jira) 


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

Prashant Satam reassigned RANGER-4427:
--

Assignee: Prashant Satam

> Need a new API to get list of datasets for a datashare with request status
> --
>
> Key: RANGER-4427
> URL: https://issues.apache.org/jira/browse/RANGER-4427
> Project: Ranger
>  Issue Type: Sub-task
>  Components: admin
>Reporter: Subhrat Chaudhary
>Assignee: Prashant Satam
>Priority: Major
>
> We need a new API to get list of datasets for a datashare with request status



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Review Request 74692: RANGER:4473:Dataset/Datashare/Shared-resource/project name should not be created with trailing spaces

2023-10-23 Thread Prashant Satam 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74692/
---

Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, Monika 
Kachhadiya, and Subhrat Chaudhary.


Repository: ranger


Description
---

Dataset/Datashare/SharedResource/project names are being created with trailing 
spaces which should not be happening since in the UI they will be seen as 
duplicate with the same names.


Diffs
-

  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 10986823d 


Diff: https://reviews.apache.org/r/74692/diff/1/


Testing
---

1)Create /Datashare/SharedResource/project with trailing spaces 
2)The response we receive after POST will not have trailing spaces for field 
name
 Example 
Request ---> POST - service/gds/project

Response --> 
{
"id": 3,
"guid": "7254a3b0-972a-4fe4-88af-b9fb591b812b",
"isEnabled": true,
"createdBy": "Admin",
"updatedBy": "Admin",
"createTime": 1698040479295,
"updateTime": 1698040479295,
"version": 1,
"name": "Ranger-Project-1",
"acl": {
"users": {
"admin": "ADMIN"
}
}
}


Thanks,

Prashant Satam