[jira] [Updated] (RANGER-4684) Need to update createdBy ,updatedBy field for gds objects in case the creator is deleted
[ https://issues.apache.org/jira/browse/RANGER-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4684: --- Description: Currently when the creator of dataset or any gds Object is deleted from ranger we get Error as cannot Delete the user because the mapping exist for the Gds objects for the column addedById, so when the delete operation will be performed the values for fields createdBy and updatedBy should be changed from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1 ) (was: Currently when the creator of dataset or any gds Object is deleted from ranger we get Error as cannot Delete the user because the mapping exist for the Gds objects for the column addedById, so when the delete operation will be performed the values for fields createdBy and updatedBy should be changed from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1)) > Need to update createdBy ,updatedBy field for gds objects in case the creator > is deleted > > > Key: RANGER-4684 > URL: https://issues.apache.org/jira/browse/RANGER-4684 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently when the creator of dataset or any gds Object is deleted from > ranger we get Error as cannot Delete the user because the mapping exist for > the Gds objects for the column addedById, so when the delete operation will > be performed the values for fields createdBy and updatedBy should be changed > from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1 ) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4684) Need to update createdBy ,updatedBy field for gds objects in case the creator is deleted
[ https://issues.apache.org/jira/browse/RANGER-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4684: -- Assignee: Prashant Satam > Need to update createdBy ,updatedBy field for gds objects in case the creator > is deleted > > > Key: RANGER-4684 > URL: https://issues.apache.org/jira/browse/RANGER-4684 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently when the creator of dataset or any gds Object is deleted from > ranger we get Error as cannot Delete the user because the mapping exist for > the Gds objects for the column addedById, so when the delete operation will > be performed the values for fields createdBy and updatedBy should be changed > from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4684) Need to update createdBy ,updatedBy field for gds objects in case the creator is deleted
[ https://issues.apache.org/jira/browse/RANGER-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4684: --- Description: Currently when the creator of dataset or any gds Object is deleted from ranger we get Error as cannot Delete the user because the mapping exist for the Gds objects for the column addedById, so when the delete operation will be performed the values for fields createdBy and updatedBy should be changed from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1) > Need to update createdBy ,updatedBy field for gds objects in case the creator > is deleted > > > Key: RANGER-4684 > URL: https://issues.apache.org/jira/browse/RANGER-4684 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently when the creator of dataset or any gds Object is deleted from > ranger we get Error as cannot Delete the user because the mapping exist for > the Gds objects for the column addedById, so when the delete operation will > be performed the values for fields createdBy and updatedBy should be changed > from the creator to the Ranger Admin (the seeded Ranger Admin having Id 1) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4684) Need to update createdBy ,updatedBy field for gds objects in case the creator is deleted
Prashant Satam created RANGER-4684: -- Summary: Need to update createdBy ,updatedBy field for gds objects in case the creator is deleted Key: RANGER-4684 URL: https://issues.apache.org/jira/browse/RANGER-4684 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4682) Need a Export API for tagResourceMaps
[ https://issues.apache.org/jira/browse/RANGER-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4682: --- Description: Currently we dont have a Export api for tagResourceMaps it will be helpful if we have a export API in format (csv,excel,json) > Need a Export API for tagResourceMaps > - > > Key: RANGER-4682 > URL: https://issues.apache.org/jira/browse/RANGER-4682 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently we dont have a Export api for tagResourceMaps it will be helpful if > we have a export API in format (csv,excel,json) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4682) Need a Export API for tagResourceMaps
[ https://issues.apache.org/jira/browse/RANGER-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4682: -- Assignee: Prashant Satam > Need a Export API for tagResourceMaps > - > > Key: RANGER-4682 > URL: https://issues.apache.org/jira/browse/RANGER-4682 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4682) Need a Export API for tagResourceMaps
Prashant Satam created RANGER-4682: -- Summary: Need a Export API for tagResourceMaps Key: RANGER-4682 URL: https://issues.apache.org/jira/browse/RANGER-4682 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4671: --- Attachment: (was: image-2024-01-23-12-20-46-315.png) > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > Attachments: Regression.png > > > There was change in behaviour of DatasetInDataShare Object for below > mentioned 2 cases > case 1 : > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to GRANTED the response is 200 expected > response is 400 with validation message stating (Not a ADMIN for dataset) > case 2: > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to DENIED the response is 200 expected response > is 400 with validation message stating (Not a ADMIN for dataset) > The Below image describes the 2 cases and its behaviour Before the change > (currently we get Response as 200 ) > !Regression.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4671: --- Attachment: (was: Regression-Behaviour.png) > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > Attachments: Regression.png > > > There was change in behaviour of DatasetInDataShare Object for below > mentioned 2 cases > case 1 : > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to GRANTED the response is 200 expected > response is 400 with validation message stating (Not a ADMIN for dataset) > case 2: > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to DENIED the response is 200 expected response > is 400 with validation message stating (Not a ADMIN for dataset) > The Below image describes the 2 cases and its behaviour Before the change > (currently we get Response as 200 ) > !Regression.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4671: --- Description: There was change in behaviour of DatasetInDataShare Object for below mentioned 2 cases case 1 : 1) create a user with Ranger ROLE as ROLE_USER 2)create a dataShare with the same user's account so the user will be dataShare Admin 3)create a dataset the above user should be absent in dataset ACL 4)create DatasetInDataShare object for these dataset,dataShare with status as ACTIVE 5)update this DatasetInDataShare object by the above created user's account change the status from ACTIVE to GRANTED the response is 200 expected response is 400 with validation message stating (Not a ADMIN for dataset) case 2: 1) create a user with Ranger ROLE as ROLE_USER 2)create a dataShare with the same user's account so the user will be dataShare Admin 3)create a dataset the above user should be absent in dataset ACL 4)create DatasetInDataShare object for these dataset,dataShare with status as ACTIVE 5)update this DatasetInDataShare object by the above created user's account change the status from ACTIVE to DENIED the response is 200 expected response is 400 with validation message stating (Not a ADMIN for dataset) The Below image describes the 2 cases and its behaviour Before the change (currently we get Response as 200 ) !Regression.png! was: There was change in behaviour of DatasetInDataShare Object for below mentioned 2 cases case 1 : 1) create a user with Ranger ROLE as ROLE_USER 2)create a dataShare with the same user's account so the user will be dataShare Admin 3)create a dataset the above user should be absent in dataset ACL 4)create DatasetInDataShare object for these dataset,dataShare with status as ACTIVE 5)update this DatasetInDataShare object by the above created user's account change the status from ACTIVE to GRANTED the response is 200 expected response is 400 with validation message stating (Not a ADMIN for dataset) case 2: 1) create a user with Ranger ROLE as ROLE_USER 2)create a dataShare with the same user's account so the user will be dataShare Admin 3)create a dataset the above user should be absent in dataset ACL 4)create DatasetInDataShare object for these dataset,dataShare with status as ACTIVE 5)update this DatasetInDataShare object by the above created user's account change the status from ACTIVE to DENIED the response is 200 expected response is 400 with validation message stating (Not a ADMIN for dataset) !image-2024-01-23-12-20-46-315.png! > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > Attachments: Regression-Behaviour.png, Regression.png, > image-2024-01-23-12-20-46-315.png > > > There was change in behaviour of DatasetInDataShare Object for below > mentioned 2 cases > case 1 : > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to GRANTED the response is 200 expected > response is 400 with validation message stating (Not a ADMIN for dataset) > case 2: > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to DENIED the response is 200 expected response > is 400 with validation message stating (Not a ADMIN for dataset) > The Below image describes the 2 cases and its behaviour Before the change > (currently we get Response as 200 ) > !Regression.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4671: --- Attachment: Regression.png > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > Attachments: Regression-Behaviour.png, Regression.png, > image-2024-01-23-12-20-46-315.png > > > There was change in behaviour of DatasetInDataShare Object for below > mentioned 2 cases > case 1 : > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to GRANTED the response is 200 expected > response is 400 with validation message stating (Not a ADMIN for dataset) > case 2: > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to DENIED the response is 200 expected response > is 400 with validation message stating (Not a ADMIN for dataset) > > !image-2024-01-23-12-20-46-315.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4671: --- Attachment: Regression-Behaviour.png > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > Attachments: Regression-Behaviour.png, > image-2024-01-23-12-20-46-315.png > > > There was change in behaviour of -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4671: --- Attachment: image-2024-01-23-12-20-46-315.png > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > Attachments: Regression-Behaviour.png, > image-2024-01-23-12-20-46-315.png > > > There was change in behaviour of -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4671: --- Description: There was change in behaviour of DatasetInDataShare Object for below mentioned 2 cases case 1 : 1) create a user with Ranger ROLE as ROLE_USER 2)create a dataShare with the same user's account so the user will be dataShare Admin 3)create a dataset the above user should be absent in dataset ACL 4)create DatasetInDataShare object for these dataset,dataShare with status as ACTIVE 5)update this DatasetInDataShare object by the above created user's account change the status from ACTIVE to GRANTED the response is 200 expected response is 400 with validation message stating (Not a ADMIN for dataset) case 2: 1) create a user with Ranger ROLE as ROLE_USER 2)create a dataShare with the same user's account so the user will be dataShare Admin 3)create a dataset the above user should be absent in dataset ACL 4)create DatasetInDataShare object for these dataset,dataShare with status as ACTIVE 5)update this DatasetInDataShare object by the above created user's account change the status from ACTIVE to DENIED the response is 200 expected response is 400 with validation message stating (Not a ADMIN for dataset) !image-2024-01-23-12-20-46-315.png! was:There was change in behaviour of > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > Attachments: Regression-Behaviour.png, > image-2024-01-23-12-20-46-315.png > > > There was change in behaviour of DatasetInDataShare Object for below > mentioned 2 cases > case 1 : > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to GRANTED the response is 200 expected > response is 400 with validation message stating (Not a ADMIN for dataset) > case 2: > 1) create a user with Ranger ROLE as ROLE_USER > 2)create a dataShare with the same user's account so the user will be > dataShare Admin > 3)create a dataset the above user should be absent in dataset ACL > 4)create DatasetInDataShare object for these dataset,dataShare with status as > ACTIVE > 5)update this DatasetInDataShare object by the above created user's account > change the status from ACTIVE to DENIED the response is 200 expected response > is 400 with validation message stating (Not a ADMIN for dataset) > > !image-2024-01-23-12-20-46-315.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4671: --- Description: There was change in behaviour of > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > There was change in behaviour of -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
[ https://issues.apache.org/jira/browse/RANGER-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4671: -- Assignee: Prashant Satam > Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases > -- > > Key: RANGER-4671 > URL: https://issues.apache.org/jira/browse/RANGER-4671 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4671) Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases
Prashant Satam created RANGER-4671: -- Summary: Noticed a change in Behaviour of DatasetInDataShare Object for 2 cases Key: RANGER-4671 URL: https://issues.apache.org/jira/browse/RANGER-4671 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4665) Need a validation message while creating SharedResource with empty Resources
[ https://issues.apache.org/jira/browse/RANGER-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam resolved RANGER-4665. Resolution: Invalid > Need a validation message while creating SharedResource with empty Resources > > > Key: RANGER-4665 > URL: https://issues.apache.org/jira/browse/RANGER-4665 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4665) Need a validation message while creating SharedResource with empty Resources
Prashant Satam created RANGER-4665: -- Summary: Need a validation message while creating SharedResource with empty Resources Key: RANGER-4665 URL: https://issues.apache.org/jira/browse/RANGER-4665 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4665) Need a validation message while creating SharedResource with empty Resources
[ https://issues.apache.org/jira/browse/RANGER-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4665: -- Assignee: Prashant Satam > Need a validation message while creating SharedResource with empty Resources > > > Key: RANGER-4665 > URL: https://issues.apache.org/jira/browse/RANGER-4665 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4614) GDS : Need new apis to get audit history of dataset/datashare
[ https://issues.apache.org/jira/browse/RANGER-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4614: -- Assignee: Prashant Satam > GDS : Need new apis to get audit history of dataset/datashare > - > > Key: RANGER-4614 > URL: https://issues.apache.org/jira/browse/RANGER-4614 > Project: Ranger > Issue Type: Task > Components: admin >Reporter: Anand Nadar >Assignee: Prashant Satam >Priority: Major > > Need api to get the audit log of a particular dataset/datashare. > Dataset history should contain > 1. Changes on dataset object > 2. Change on dataset policy > 3. Changes on DatashareInDataset object. > Datashare history should contain > 1. Changes on Datashare object. > 2. Changes on its SharedResources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4662) GdsVersion should update after deleting user,group
[
https://issues.apache.org/jira/browse/RANGER-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4662:
---
Description:
Currently when we delete user,group which is referenced in gds policy then
GdsVersion ()is not updated after the action it needs to be updated.
Steps :
1)create a user and resource service
2)create a dataset , and dataShare (with the resource service),and a
sharedResource (with dataShare),also create mapping of dataset with dataShare
as ACTIVE
3)create a GDS policy for the dataset
4)Update dataset policy and add created user to it for this actions the
GdsVersion is updated we can check by (GET API
/service/gds/download/\{serviceName})
5)but when we delete the created user then the GdsVersion is not updated we
need to update it
was:
Currently when we delete user,group which is referenced in gds policy then
GdsVersion ()is not updated after the action it needs to be updated.
Steps :
1)create a user and resource service
2)create a dataset , and dataShare (with the resource service),and a
sharedResource (with dataShare),also create mapping of dataset with dataShare
as ACTIVE
3)create a GDS policy for the dataset
4)Update dataset policy and add created user to it for this actions the
GdsVersion is updated we can check by (GET API
/service/gds/download/\{serviceName})
5)but when we delete the created user then the GdsVersion is not updated
> GdsVersion should update after deleting user,group
> ---
>
> Key: RANGER-4662
> URL: https://issues.apache.org/jira/browse/RANGER-4662
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Currently when we delete user,group which is referenced in gds policy then
> GdsVersion ()is not updated after the action it needs to be updated.
> Steps :
> 1)create a user and resource service
> 2)create a dataset , and dataShare (with the resource service),and a
> sharedResource (with dataShare),also create mapping of dataset with dataShare
> as ACTIVE
> 3)create a GDS policy for the dataset
> 4)Update dataset policy and add created user to it for this actions the
> GdsVersion is updated we can check by (GET API
> /service/gds/download/\{serviceName})
> 5)but when we delete the created user then the GdsVersion is not updated we
> need to update it
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4662) GdsVersion should update after deleting user,group
[
https://issues.apache.org/jira/browse/RANGER-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam reassigned RANGER-4662:
--
Assignee: Prashant Satam
> GdsVersion should update after deleting user,group
> ---
>
> Key: RANGER-4662
> URL: https://issues.apache.org/jira/browse/RANGER-4662
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Currently when we delete user,group which is referenced in gds policy then
> GdsVersion ()is not updated after the action it needs to be updated.
> Steps :
> 1)create a user and resource service
> 2)create a dataset , and dataShare (with the resource service),and a
> sharedResource (with dataShare),also create mapping of dataset with dataShare
> as ACTIVE
> 3)create a GDS policy for the dataset
> 4)Update dataset policy and add created user to it for this actions the
> GdsVersion is updated we can check by (GET API
> /service/gds/download/\{serviceName})
> 5)but when we delete the created user then the GdsVersion is not updated
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4662) GdsVersion should update after deleting user,group
[
https://issues.apache.org/jira/browse/RANGER-4662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4662:
---
Description:
Currently when we delete user,group which is referenced in gds policy then
GdsVersion ()is not updated after the action it needs to be updated.
Steps :
1)create a user and resource service
2)create a dataset , and dataShare (with the resource service),and a
sharedResource (with dataShare),also create mapping of dataset with dataShare
as ACTIVE
3)create a GDS policy for the dataset
4)Update dataset policy and add created user to it for this actions the
GdsVersion is updated we can check by (GET API
/service/gds/download/\{serviceName})
5)but when we delete the created user then the GdsVersion is not updated
> GdsVersion should update after deleting user,group
> ---
>
> Key: RANGER-4662
> URL: https://issues.apache.org/jira/browse/RANGER-4662
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Prashant Satam
>Priority: Major
>
> Currently when we delete user,group which is referenced in gds policy then
> GdsVersion ()is not updated after the action it needs to be updated.
> Steps :
> 1)create a user and resource service
> 2)create a dataset , and dataShare (with the resource service),and a
> sharedResource (with dataShare),also create mapping of dataset with dataShare
> as ACTIVE
> 3)create a GDS policy for the dataset
> 4)Update dataset policy and add created user to it for this actions the
> GdsVersion is updated we can check by (GET API
> /service/gds/download/\{serviceName})
> 5)but when we delete the created user then the GdsVersion is not updated
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4662) GdsVersion should update after deleting user,group
Prashant Satam created RANGER-4662: -- Summary: GdsVersion should update after deleting user,group Key: RANGER-4662 URL: https://issues.apache.org/jira/browse/RANGER-4662 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4651) Need to update Gds objects ACL if ranger principal is deleted
[ https://issues.apache.org/jira/browse/RANGER-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4651: -- Assignee: Prashant Satam Patch in review => [https://reviews.apache.org/r/74836/diff/1#index_header] > Need to update Gds objects ACL if ranger principal is deleted > - > > Key: RANGER-4651 > URL: https://issues.apache.org/jira/browse/RANGER-4651 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently if any principal i.e user/group/role stored in ranger is deleted > the GdsObject ACLs still have this principals they dont get removed from the > ACL we need to remove this principals from gdsObject ACLs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4651) Need to update Gds objects ACL if ranger principal is deleted
[ https://issues.apache.org/jira/browse/RANGER-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4651: --- Issue Type: Bug (was: Improvement) > Need to update Gds objects ACL if ranger principal is deleted > - > > Key: RANGER-4651 > URL: https://issues.apache.org/jira/browse/RANGER-4651 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently if any principal i.e user/group/role stored in ranger is deleted > the GdsObject ACLs still have this principals they dont get removed from the > ACL we need to remove this principals from gdsObject ACLs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4651) Need to update Gds objects ACL if ranger principal is deleted
[ https://issues.apache.org/jira/browse/RANGER-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4651: --- Description: Currently if any principal i.e user/group/role stored in ranger is deleted the GdsObject ACLs still have this principals they dont get removed from the ACL we need to remove this principals from gdsObject ACLs (was: Currently if any principal i.e user/group/role stored in ranger is ) > Need to update Gds objects ACL if ranger principal is deleted > - > > Key: RANGER-4651 > URL: https://issues.apache.org/jira/browse/RANGER-4651 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently if any principal i.e user/group/role stored in ranger is deleted > the GdsObject ACLs still have this principals they dont get removed from the > ACL we need to remove this principals from gdsObject ACLs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4651) Need to update Gds objects ACL as per changes in Ranger principals
[ https://issues.apache.org/jira/browse/RANGER-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4651: --- Description: Currently if any principal i.e user/group/role stored in ranger is > Need to update Gds objects ACL as per changes in Ranger principals > -- > > Key: RANGER-4651 > URL: https://issues.apache.org/jira/browse/RANGER-4651 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently if any principal i.e user/group/role stored in ranger is -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4651) Need to update Gds objects ACL if ranger principal is deleted
[ https://issues.apache.org/jira/browse/RANGER-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4651: --- Summary: Need to update Gds objects ACL if ranger principal is deleted (was: Need to update Gds objects ACL as per changes in Ranger principals) > Need to update Gds objects ACL if ranger principal is deleted > - > > Key: RANGER-4651 > URL: https://issues.apache.org/jira/browse/RANGER-4651 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently if any principal i.e user/group/role stored in ranger is -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4651) Need to update Gds objects ACL as per changes in Ranger principals
Prashant Satam created RANGER-4651: -- Summary: Need to update Gds objects ACL as per changes in Ranger principals Key: RANGER-4651 URL: https://issues.apache.org/jira/browse/RANGER-4651 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4649) Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST
[ https://issues.apache.org/jira/browse/RANGER-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4649: --- Description: There are junit test case failure in : TestServiceREST > test71DeleteClusterServices, TestAssetREST ---> testCountXAssets, was: There are junit test case failure in : TestServiceREST > test71DeleteClusterServices > Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST > > > Key: RANGER-4649 > URL: https://issues.apache.org/jira/browse/RANGER-4649 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > There are junit test case failure in : > TestServiceREST > test71DeleteClusterServices, > TestAssetREST ---> testCountXAssets, > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4649) Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST
[ https://issues.apache.org/jira/browse/RANGER-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4649: --- Description: There are junit test case failure in : TestServiceREST > test71DeleteClusterServices, TestAssetREST ---> testCountXAssets, TestXAuditREST --> Test7searchXAccessAudits was: There are junit test case failure in : TestServiceREST > test71DeleteClusterServices, TestAssetREST ---> testCountXAssets, > Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST > > > Key: RANGER-4649 > URL: https://issues.apache.org/jira/browse/RANGER-4649 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > There are junit test case failure in : > TestServiceREST > test71DeleteClusterServices, > TestAssetREST ---> testCountXAssets, > TestXAuditREST --> Test7searchXAccessAudits > > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4649) Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST
[ https://issues.apache.org/jira/browse/RANGER-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4649: --- Description: There are junit test case failure in : TestServiceREST > test71DeleteClusterServices was: There are junit test case failure in : > Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST > > > Key: RANGER-4649 > URL: https://issues.apache.org/jira/browse/RANGER-4649 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > There are junit test case failure in : > TestServiceREST > test71DeleteClusterServices > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4649) Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST
[ https://issues.apache.org/jira/browse/RANGER-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4649: --- Description: There are junit test case failure in : > Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST > > > Key: RANGER-4649 > URL: https://issues.apache.org/jira/browse/RANGER-4649 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > There are junit test case failure in : > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4649) Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST
[ https://issues.apache.org/jira/browse/RANGER-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4649: --- Description: There are junit test case failure in : was: There are junit test case failure in : > Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST > > > Key: RANGER-4649 > URL: https://issues.apache.org/jira/browse/RANGER-4649 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > There are junit test case failure in : > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4649) Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST
[ https://issues.apache.org/jira/browse/RANGER-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4649: -- Assignee: Prashant Satam > Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST > > > Key: RANGER-4649 > URL: https://issues.apache.org/jira/browse/RANGER-4649 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4649) Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST
Prashant Satam created RANGER-4649: -- Summary: Junit failing in TestServiceREST , TestAssetREST, TestXAuditREST Key: RANGER-4649 URL: https://issues.apache.org/jira/browse/RANGER-4649 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4634) Need cascade delete for service
[ https://issues.apache.org/jira/browse/RANGER-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4634: -- Assignee: Prashant Satam > Need cascade delete for service > --- > > Key: RANGER-4634 > URL: https://issues.apache.org/jira/browse/RANGER-4634 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently when we delete a service which has datashares and related > entities(i.e shared-resources, dataShareInDatasets) connected to it we get > error while deleting the service. > It is Expected that we should be able to delete the service by cascade > deleting the datashares and related entities connected to this service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4634) Need cascade delete for service
[ https://issues.apache.org/jira/browse/RANGER-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4634: --- Description: Currently when we delete a service which has datashares and related entities(i.e shared-resources, dataShareInDatasets) connected to it we get error while deleting the service. It is Expected that we should be able to delete the service by cascade deleting the datashares and related entities connected to this service was: Currently when we delete a service which has datashares and related entities connected to it we get error while deleting the service. It is Expected that we should be able to delete the service by cascade deleting the datashares and related entities connected to this service > Need cascade delete for service > --- > > Key: RANGER-4634 > URL: https://issues.apache.org/jira/browse/RANGER-4634 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently when we delete a service which has datashares and related > entities(i.e shared-resources, dataShareInDatasets) connected to it we get > error while deleting the service. > It is Expected that we should be able to delete the service by cascade > deleting the datashares and related entities connected to this service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4634) Need cascade delete for service
[ https://issues.apache.org/jira/browse/RANGER-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4634: --- Description: Currently when we delete a service which has datashares and related entities connected to it we get error while deleting the service. It is Expected that we should be able to delete the service by cascade deleting the datashares and related entities connected to this service > Need cascade delete for service > --- > > Key: RANGER-4634 > URL: https://issues.apache.org/jira/browse/RANGER-4634 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently when we delete a service which has datashares and related entities > connected to it we get error while deleting the service. > It is Expected that we should be able to delete the service by cascade > deleting the datashares and related entities connected to this service -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4634) Need cascade delete for service
Prashant Satam created RANGER-4634: -- Summary: Need cascade delete for service Key: RANGER-4634 URL: https://issues.apache.org/jira/browse/RANGER-4634 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4633) Need to generate Admin Audits for tag and tagdef
[ https://issues.apache.org/jira/browse/RANGER-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4633: -- Assignee: Prashant Satam > Need to generate Admin Audits for tag and tagdef > - > > Key: RANGER-4633 > URL: https://issues.apache.org/jira/browse/RANGER-4633 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently when we ADD/UPDATE/DELETE tag and tagdef we dont generate > Transaction logs for it so we dont get Admin Audits for this operations it > will be helpful if we generate them -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4633) Need to generate Admin Audits for tag and tagdef
[ https://issues.apache.org/jira/browse/RANGER-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4633: --- Description: Currently when we ADD/UPDATE/DELETE tag and tagdef we dont generate Transaction logs for it so we dont get Admin Audits for this operations it will be helpful if we generate them > Need to generate Admin Audits for tag and tagdef > - > > Key: RANGER-4633 > URL: https://issues.apache.org/jira/browse/RANGER-4633 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently when we ADD/UPDATE/DELETE tag and tagdef we dont generate > Transaction logs for it so we dont get Admin Audits for this operations it > will be helpful if we generate them -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4633) Need to generate Admin Audits for tag and tagdef
Prashant Satam created RANGER-4633: -- Summary: Need to generate Admin Audits for tag and tagdef Key: RANGER-4633 URL: https://issues.apache.org/jira/browse/RANGER-4633 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4630) Need to add pagination support and searchFilters for tag related APIs
[ https://issues.apache.org/jira/browse/RANGER-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4630: --- Description: Currently for Tag related GET-APIs i.e for (RangerTags,RangerTagDefs,RangerServiceResource) we dont support pagination,and also we need additional searchFilters for them > Need to add pagination support and searchFilters for tag related APIs > - > > Key: RANGER-4630 > URL: https://issues.apache.org/jira/browse/RANGER-4630 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Minor > > Currently for Tag related GET-APIs i.e for > (RangerTags,RangerTagDefs,RangerServiceResource) we dont support > pagination,and also we need additional searchFilters for them -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4630) Need to add pagination support and searchFilters for tag related APIs
[ https://issues.apache.org/jira/browse/RANGER-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4630: -- Assignee: Prashant Satam > Need to add pagination support and searchFilters for tag related APIs > - > > Key: RANGER-4630 > URL: https://issues.apache.org/jira/browse/RANGER-4630 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4630) Need to add pagination support and searchFilters for tag related APIs
Prashant Satam created RANGER-4630: -- Summary: Need to add pagination support and searchFilters for tag related APIs Key: RANGER-4630 URL: https://issues.apache.org/jira/browse/RANGER-4630 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4393) with direct API call, ranger is allowing to add more than 1 dataset in a dataset policy
[ https://issues.apache.org/jira/browse/RANGER-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam resolved RANGER-4393. Resolution: Invalid > with direct API call, ranger is allowing to add more than 1 dataset in a > dataset policy > --- > > Key: RANGER-4393 > URL: https://issues.apache.org/jira/browse/RANGER-4393 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > With direct API call, ranger is allowing to add more than 1 dataset > i.e(datasetName) in a dataset policy. It is blocked from UI. We need to block > it from backend also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (RANGER-4494) get Dataset summary for logged in user based on dataset-policy.
[ https://issues.apache.org/jira/browse/RANGER-4494 ] Prashant Satam deleted comment on RANGER-4494: was (Author: JIRAUSER300185): Patch in Review --> https://reviews.apache.org/r/74697/ > get Dataset summary for logged in user based on dataset-policy. > --- > > Key: RANGER-4494 > URL: https://issues.apache.org/jira/browse/RANGER-4494 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > We need a new API URI--->(/dataset/summary/sharedwithme) to extend the > /dataset/summary API added in > https://issues.apache.org/jira/browse/RANGER-4446, to get the DatasetSummary > for datasets which are shared with the logged in user, based on policy. > Use of The API > This API will return dataset summary objects which are accessible for the > logged in user by the dataset policy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4490) Need new API for DataShare in Dataset Summary
[ 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) Details of the API FIELDS (datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based on dataShare),zoneName,shareStatus,) Supported Query Params datasetName,dataShareName,datasetNamePartial,dataShareNamePartial,approver,shareStatus,createdBy,serviceName,zoneName,serviceId,zoneId 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) > Details of the API > FIELDS > (datasetId,datasetName,dataShareId,dataShareName,serviceId,serviceName,zoneId,resoueceCount(based > on dataShare),zoneName,shareStatus,) > Supported Query Params > datasetName,dataShareName,datasetNamePartial,dataShareNamePartial,approver,shareStatus,createdBy,serviceName,zoneName,serviceId,zoneId -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4629) We need ACL evaluation in GET API for shared-resource
[ https://issues.apache.org/jira/browse/RANGER-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4629: --- Description: Currently there is no validation for GET API of shared-resource we need to add ACL evaluation (i.e respective dataShares ACL evaluation) for the GET API of shared resource > We need ACL evaluation in GET API for shared-resource > - > > Key: RANGER-4629 > URL: https://issues.apache.org/jira/browse/RANGER-4629 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > Currently there is no validation for GET API of shared-resource we need to > add ACL evaluation (i.e respective dataShares ACL evaluation) for the GET API > of shared resource -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4629) We need ACL evaluation in GET API for shared-resource
[ https://issues.apache.org/jira/browse/RANGER-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4629: -- Assignee: Prashant Satam > We need ACL evaluation in GET API for shared-resource > - > > Key: RANGER-4629 > URL: https://issues.apache.org/jira/browse/RANGER-4629 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently there is no validation for GET API of shared-resource we need to > add ACL evaluation (i.e respective dataShares ACL evaluation) for the GET API > of shared resource -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4629) We need ACL evaluation in GET API for shared-resource
Prashant Satam created RANGER-4629: -- Summary: We need ACL evaluation in GET API for shared-resource Key: RANGER-4629 URL: https://issues.apache.org/jira/browse/RANGER-4629 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4628) Need to add Validations for Security-Zone partial update API
[
https://issues.apache.org/jira/browse/RANGER-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4628:
---
Description:
For Partial Update of Security-Zone API ===>
/service/public/v2/api/zones-v2/\{id}/partial
1)We can add existing admins/auditors to the zone and still get 200 as response
2)We can add existing tagServices to the zone and still get 200 as response
3)While removing the existing resources in zone if we pass invalid serviceName
we still get 200 as response though the zone is not getting updated
> Need to add Validations for Security-Zone partial update API
>
>
> Key: RANGER-4628
> URL: https://issues.apache.org/jira/browse/RANGER-4628
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> For Partial Update of Security-Zone API ===>
> /service/public/v2/api/zones-v2/\{id}/partial
> 1)We can add existing admins/auditors to the zone and still get 200 as
> response
> 2)We can add existing tagServices to the zone and still get 200 as response
> 3)While removing the existing resources in zone if we pass invalid
> serviceName we still get 200 as response though the zone is not getting
> updated
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4628) Need to add Validations for Security-Zone partial update API
[ https://issues.apache.org/jira/browse/RANGER-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4628: -- Assignee: Prashant Satam > Need to add Validations for Security-Zone partial update API > > > Key: RANGER-4628 > URL: https://issues.apache.org/jira/browse/RANGER-4628 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4628) Need to add Validations for Security-Zone partial update API
Prashant Satam created RANGER-4628: -- Summary: Need to add Validations for Security-Zone partial update API Key: RANGER-4628 URL: https://issues.apache.org/jira/browse/RANGER-4628 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4618) Need to add displayName field in zoneSummary Object
[ https://issues.apache.org/jira/browse/RANGER-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4618: --- Description: In the zoneSummary Object services section we have name field to display serviceName but it will be helpful if we add displayName field also to the same > Need to add displayName field in zoneSummary Object > --- > > Key: RANGER-4618 > URL: https://issues.apache.org/jira/browse/RANGER-4618 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > In the zoneSummary Object services section we have name field to display > serviceName but it will be helpful if we add displayName field also to the > same -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4618) Need to add displayName field in zoneSummary Object
Prashant Satam created RANGER-4618: -- Summary: Need to add displayName field in zoneSummary Object Key: RANGER-4618 URL: https://issues.apache.org/jira/browse/RANGER-4618 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4618) Need to add displayName field in zoneSummary Object
[ https://issues.apache.org/jira/browse/RANGER-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4618: -- Assignee: Prashant Satam > Need to add displayName field in zoneSummary Object > --- > > Key: RANGER-4618 > URL: https://issues.apache.org/jira/browse/RANGER-4618 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4617) Need to add ACL principal details in dataset summary API
[ https://issues.apache.org/jira/browse/RANGER-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4617: --- Description: Currently in dataset-summary API we have a field "principalsCount" which gives details of principal in dataset policy ,Also adding field "aclPrincipalsCount" which will give details of principals in dataset ACL will also be helpful for getting more information for a dataset > Need to add ACL principal details in dataset summary API > - > > Key: RANGER-4617 > URL: https://issues.apache.org/jira/browse/RANGER-4617 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently in dataset-summary API we have a field > "principalsCount" which gives details of principal in dataset policy ,Also > adding field "aclPrincipalsCount" which will give details of principals in > dataset ACL will also be helpful for getting more information for a dataset -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4617) Need to add ACL principal details in dataset summary API
Prashant Satam created RANGER-4617: -- Summary: Need to add ACL principal details in dataset summary API Key: RANGER-4617 URL: https://issues.apache.org/jira/browse/RANGER-4617 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4617) Need to add ACL principal details in dataset summary API
[ https://issues.apache.org/jira/browse/RANGER-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4617: -- Assignee: Prashant Satam > Need to add ACL principal details in dataset summary API > - > > Key: RANGER-4617 > URL: https://issues.apache.org/jira/browse/RANGER-4617 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4608) Need to add ACL evaluation for get datashare by ID API
[ https://issues.apache.org/jira/browse/RANGER-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4608: --- Description: For GET API for datashare by ID need to add ACL evaluation (was: For GET API of datashare by ID need to add ACL evaluation ) > Need to add ACL evaluation for get datashare by ID API > --- > > Key: RANGER-4608 > URL: https://issues.apache.org/jira/browse/RANGER-4608 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > For GET API for datashare by ID need to add ACL evaluation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4608) Need to add ACL evaluation for get datashare by ID API
Prashant Satam created RANGER-4608: -- Summary: Need to add ACL evaluation for get datashare by ID API Key: RANGER-4608 URL: https://issues.apache.org/jira/browse/RANGER-4608 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam For GET API of datashare by ID need to add ACL evaluation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4604) Need to add query param createdBy for security-zone GET API
[ https://issues.apache.org/jira/browse/RANGER-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4604: --- Description: We need to add a query param createdBy for security-zone GET API. It will be useful to filter list of security-zones created by user, especially to get the security-zone created by self (was: We need to add a query param createdBy for security-zone GET API) > Need to add query param createdBy for security-zone GET API > --- > > Key: RANGER-4604 > URL: https://issues.apache.org/jira/browse/RANGER-4604 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > We need to add a query param createdBy for security-zone GET API. It will be > useful to filter list of security-zones created by user, especially to get > the security-zone created by self -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4603) Need to add query param createdBy for dataset GET API
[ https://issues.apache.org/jira/browse/RANGER-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4603: --- Description: Currently we have dataset GET APIs to get list datasets based on ACL. It will be useful to be able filter the list based on users who created the dataset, especially to get the datasets created by self. (was: Currently we have dataset GET APIs to get list datasets based on ACL. It will be useful to be able filter the list based users who created the dataset, especially to get the datasets created by self.) > Need to add query param createdBy for dataset GET API > - > > Key: RANGER-4603 > URL: https://issues.apache.org/jira/browse/RANGER-4603 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently we have dataset GET APIs to get list datasets based on ACL. It will > be useful to be able filter the list based on users who created the dataset, > especially to get the datasets created by self. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4603) Need to add query param createdBy for dataset GET API
[ https://issues.apache.org/jira/browse/RANGER-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4603: --- Description: Currently we have dataset GET APIs to get list datasets based on ACL. It will be useful to be able filter the list based users who created the dataset, especially to get the datasets created by self. (was: We need add a query param createdBy for dataset GET API it will be needed in case of (/dataset/summary) API ) > Need to add query param createdBy for dataset GET API > - > > Key: RANGER-4603 > URL: https://issues.apache.org/jira/browse/RANGER-4603 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Currently we have dataset GET APIs to get list datasets based on ACL. It will > be useful to be able filter the list based users who created the dataset, > especially to get the datasets created by self. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4604) Need to add query param createdBy for security-zone GET API
[ https://issues.apache.org/jira/browse/RANGER-4604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4604: -- Assignee: Prashant Satam > Need to add query param createdBy for security-zone GET API > --- > > Key: RANGER-4604 > URL: https://issues.apache.org/jira/browse/RANGER-4604 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > We need to add a query param createdBy for security-zone GET API -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4603) Need to add query param createdBy for dataset GET API
Prashant Satam created RANGER-4603: -- Summary: Need to add query param createdBy for dataset GET API Key: RANGER-4603 URL: https://issues.apache.org/jira/browse/RANGER-4603 Project: Ranger Issue Type: Sub-task Components: Ranger Reporter: Prashant Satam We need add a query param createdBy for dataset GET API it will be needed in case of (/dataset/summary) API -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4604) Need to add query param createdBy for security-zone GET API
Prashant Satam created RANGER-4604: -- Summary: Need to add query param createdBy for security-zone GET API Key: RANGER-4604 URL: https://issues.apache.org/jira/browse/RANGER-4604 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam We need to add a query param createdBy for security-zone GET API -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4603) Need to add query param createdBy for dataset GET API
[ https://issues.apache.org/jira/browse/RANGER-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4603: -- Assignee: Prashant Satam > Need to add query param createdBy for dataset GET API > - > > Key: RANGER-4603 > URL: https://issues.apache.org/jira/browse/RANGER-4603 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > We need add a query param createdBy for dataset GET API it will be needed in > case of (/dataset/summary) API -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4558) User is allowed to create/update sharedResource, even if the user is not zoneAdmin in the linked dataShared
[ https://issues.apache.org/jira/browse/RANGER-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4558: --- 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 > User is allowed to create/update sharedResource, even if the user is not > zoneAdmin in the linked dataShared > --- > > Key: RANGER-4558 > URL: https://issues.apache.org/jira/browse/RANGER-4558 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > 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 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4558) User is allowed to create/update sharedResource, even if the user is not zoneAdmin in the linked dataShared
[ https://issues.apache.org/jira/browse/RANGER-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4558: --- Summary: User is allowed to create/update sharedResource, even if the user is not zoneAdmin in the linked dataShared (was: User is allowed to create/update sharedResource, even if the user is not zoneAdmin the linked dataShared) > User is allowed to create/update sharedResource, even if the user is not > zoneAdmin in the linked dataShared > --- > > Key: RANGER-4558 > URL: https://issues.apache.org/jira/browse/RANGER-4558 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4558) User is allowed to create/update sharedResource, even if the user is not zoneAdmin the linked dataShared
[ https://issues.apache.org/jira/browse/RANGER-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4558: --- Summary: User is allowed to create/update sharedResource, even if the user is not zoneAdmin the linked dataShared (was: User is allowed to create/update sharedResource, even if user is not zoneAdmin the linked dataShared) > User is allowed to create/update sharedResource, even if the user is not > zoneAdmin the linked dataShared > > > Key: RANGER-4558 > URL: https://issues.apache.org/jira/browse/RANGER-4558 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4558) User is allowed to create/update sharedResource, even if user is not zoneAdmin the linked dataShared
[ https://issues.apache.org/jira/browse/RANGER-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4558: -- Assignee: Prashant Satam > User is allowed to create/update sharedResource, even if user is not > zoneAdmin the linked dataShared > > > Key: RANGER-4558 > URL: https://issues.apache.org/jira/browse/RANGER-4558 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4558) User is allowed to create/update sharedResource, even if user is not zoneAdmin the linked dataShared
Prashant Satam created RANGER-4558: -- Summary: User is allowed to create/update sharedResource, even if user is not zoneAdmin the linked dataShared Key: RANGER-4558 URL: https://issues.apache.org/jira/browse/RANGER-4558 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4542) Need to add support of search by zoneNamePartial and sort by zoneName,createTime query params in zone-summary api
[ https://issues.apache.org/jira/browse/RANGER-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4542: --- Description: For GET API service/zones/summary we need to add support for query param search by zoneNamePartial , and sort by zoneName, createTime (Both ASC and DESC order) > Need to add support of search by zoneNamePartial and sort by > zoneName,createTime query params in zone-summary api > - > > Key: RANGER-4542 > URL: https://issues.apache.org/jira/browse/RANGER-4542 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > For GET API service/zones/summary we need to add support for query param > search by zoneNamePartial , and sort by zoneName, createTime (Both ASC and > DESC order) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4542) Need to add support of search by zoneNamePartial and sort by zoneName,createTime query params in zone-summary api
[ https://issues.apache.org/jira/browse/RANGER-4542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4542: -- Assignee: Prashant Satam > Need to add support of search by zoneNamePartial and sort by > zoneName,createTime query params in zone-summary api > - > > Key: RANGER-4542 > URL: https://issues.apache.org/jira/browse/RANGER-4542 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4542) Need to add support of search by zoneNamePartial and sort by zoneName,createTime query params in zone-summary api
Prashant Satam created RANGER-4542: -- Summary: Need to add support of search by zoneNamePartial and sort by zoneName,createTime query params in zone-summary api Key: RANGER-4542 URL: https://issues.apache.org/jira/browse/RANGER-4542 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4541) Ranger admin should be able to make any possible transition in case of RangerDataShareInDataset
[ https://issues.apache.org/jira/browse/RANGER-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4541: -- Assignee: Prashant Satam > Ranger admin should be able to make any possible transition in case of > RangerDataShareInDataset > --- > > Key: RANGER-4541 > URL: https://issues.apache.org/jira/browse/RANGER-4541 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > When we create/update RangerDataShareInDataset object we check if current > user is (dataset admin/datashare admin) this step should be skipped if the > current user is Ranger-Admin > Example: > 1)From Ranger-Admin account create datashare and shared-resource > 2)From USER account create dataset > 3)From Ranger-Admin account add the datashare to dataset with status as > ACTIVE we get error ---> reason[User is not an admin for dataset] , But > the user is Ranger-Admin > 4)Expected : Ranger-Admin should be able to add datashare to dataset in > ACTIVE status directly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4541) Ranger admin should be able to make any possible transition in case of RangerDataShareInDataset
[ https://issues.apache.org/jira/browse/RANGER-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4541: --- Description: When we create/update RangerDataShareInDataset object we check if current user is (dataset admin/datashare admin) this step should be skipped if the current user is Ranger-Admin Example: 1)From Ranger-Admin account create datashare and shared-resource 2)From USER account create dataset 3)From Ranger-Admin account add the datashare to dataset with status as ACTIVE we get error ---> reason[User is not an admin for dataset] , But the user is Ranger-Admin 4)Expected : Ranger-Admin should be able to add datashare to dataset in ACTIVE status directly was:When we create/update RangerDataShareInDataset object we check if current user is (dataset admin/datashare admin) this step should be skipped if the current user is Ranger-Admin > Ranger admin should be able to make any possible transition in case of > RangerDataShareInDataset > --- > > Key: RANGER-4541 > URL: https://issues.apache.org/jira/browse/RANGER-4541 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > When we create/update RangerDataShareInDataset object we check if current > user is (dataset admin/datashare admin) this step should be skipped if the > current user is Ranger-Admin > Example: > 1)From Ranger-Admin account create datashare and shared-resource > 2)From USER account create dataset > 3)From Ranger-Admin account add the datashare to dataset with status as > ACTIVE we get error ---> reason[User is not an admin for dataset] , But > the user is Ranger-Admin > 4)Expected : Ranger-Admin should be able to add datashare to dataset in > ACTIVE status directly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4541) Ranger admin should be able to make any possible transition in case of RangerDataShareInDataset
[ https://issues.apache.org/jira/browse/RANGER-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4541: --- Description: When we create/update RangerDataShareInDataset object we check if current user is (dataset admin/datashare admin) this step should be skipped if the current user is Ranger-Admin (was: When we create/update ) > Ranger admin should be able to make any possible transition in case of > RangerDataShareInDataset > --- > > Key: RANGER-4541 > URL: https://issues.apache.org/jira/browse/RANGER-4541 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > When we create/update RangerDataShareInDataset object we check if current > user is (dataset admin/datashare admin) this step should be skipped if the > current user is Ranger-Admin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4541) Ranger admin should be able to make any possible transition in case of RangerDataShareInDataset
[ https://issues.apache.org/jira/browse/RANGER-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4541: --- Description: When we create/update > Ranger admin should be able to make any possible transition in case of > RangerDataShareInDataset > --- > > Key: RANGER-4541 > URL: https://issues.apache.org/jira/browse/RANGER-4541 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Priority: Major > > When we create/update -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4541) Ranger admin should be able to make any possible transition in case of RangerDataShareInDataset
Prashant Satam created RANGER-4541: -- Summary: Ranger admin should be able to make any possible transition in case of RangerDataShareInDataset Key: RANGER-4541 URL: https://issues.apache.org/jira/browse/RANGER-4541 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4534) Use of Query param GdsPermission with value NONE gives incorrect response for GDS GET APIs
[ https://issues.apache.org/jira/browse/RANGER-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4534: --- Description: When we use GDS GET APIs for (dataset/datashare/project) and pass query param gdsPermission=NONE we get all the objects in response which is not expected Example : When the param gdsPermission=NONE is passed in request, in the GET APIs e.g. GET /gds/dataset, whole dataset list is returned in response, even if the calling user is not added in the ACLs in any of the datasets. was: When we use GDS GET APIs for (dataset/datashare/project) and pass query param gdsPermission=NONE we get all the objects in response which is not expected Example : 1)We have 4 datasets created 2)Test-User has ADMIN access to 2 datasets only for remaining 2 datasets, Test-User has no permission in ACL of dataset 3)Still when Test-User use GET API ---> /service/gds/dataset with query param gdsPermission = NONE he gets all the 4 datasets in response which is not expected > Use of Query param GdsPermission with value NONE gives incorrect response for > GDS GET APIs > -- > > Key: RANGER-4534 > URL: https://issues.apache.org/jira/browse/RANGER-4534 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > When we use GDS GET APIs for (dataset/datashare/project) and pass query param > gdsPermission=NONE we get all the objects in response which is not expected > Example : > When the param gdsPermission=NONE is passed in request, in the GET APIs e.g. > GET /gds/dataset, whole dataset list is returned in response, even if the > calling user is not added in the ACLs in any of the datasets. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4534) Use of Query param GdsPermission with value NONE gives incorrect response for GDS GET APIs
[ https://issues.apache.org/jira/browse/RANGER-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam updated RANGER-4534: --- Description: When we use GDS GET APIs for (dataset/datashare/project) and pass query param gdsPermission=NONE we get all the objects in response which is not expected Example : 1)We have 4 datasets created 2)Test-User has ADMIN access to 2 datasets only for remaining 2 datasets, Test-User has no permission in ACL of dataset 3)Still when Test-User use GET API ---> /service/gds/dataset with query param gdsPermission = NONE he gets all the 4 datasets in response which is not expected > Use of Query param GdsPermission with value NONE gives incorrect response for > GDS GET APIs > -- > > Key: RANGER-4534 > URL: https://issues.apache.org/jira/browse/RANGER-4534 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > When we use GDS GET APIs for (dataset/datashare/project) and pass query param > gdsPermission=NONE we get all the objects in response which is not expected > Example : > 1)We have 4 datasets created > 2)Test-User has ADMIN access to 2 datasets only for remaining 2 datasets, > Test-User has no permission in ACL of dataset > 3)Still when Test-User use GET API ---> /service/gds/dataset with query param > gdsPermission = NONE he gets all the 4 datasets in response which is not > expected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4534) Use of Query param GdsPermission with value NONE gives incorrect response for GDS GET APIs
[ https://issues.apache.org/jira/browse/RANGER-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4534: -- Assignee: Prashant Satam > Use of Query param GdsPermission with value NONE gives incorrect response for > GDS GET APIs > -- > > Key: RANGER-4534 > URL: https://issues.apache.org/jira/browse/RANGER-4534 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4534) Use of Query param GdsPermission with value NONE gives incorrect response for GDS GET APIs
Prashant Satam created RANGER-4534: -- Summary: Use of Query param GdsPermission with value NONE gives incorrect response for GDS GET APIs Key: RANGER-4534 URL: https://issues.apache.org/jira/browse/RANGER-4534 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4397) API to get DataShare id,name,description List
[ https://issues.apache.org/jira/browse/RANGER-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam resolved RANGER-4397. Resolution: Fixed > API to get DataShare id,name,description List > -- > > Key: RANGER-4397 > URL: https://issues.apache.org/jira/browse/RANGER-4397 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > Dataset Details >> Add a Datashare >> List Datashares pop up, > Need a GET API to get all datashares, based on LIST ACL for current user > Exclude existing one for which request is is available GRANTED, ACTIVE, > REQUESTED states > Response: id, Name, Descrption > Request: datasetId, excludeExistingDataShare > Filter: partial search on datashare name, Pagination -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4491) Need new API for DataShare in Dataset Summary
[ https://issues.apache.org/jira/browse/RANGER-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam resolved RANGER-4491. Resolution: Duplicate > Need new API for DataShare in Dataset Summary > -- > > Key: RANGER-4491 > URL: https://issues.apache.org/jira/browse/RANGER-4491 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Prashant Satam >Priority: Major > Labels: invald > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4489) Need new API for DataShare in Dataset Summary
[ https://issues.apache.org/jira/browse/RANGER-4489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam resolved RANGER-4489. Resolution: Duplicate > Need new API for DataShare in Dataset Summary > -- > > Key: RANGER-4489 > URL: https://issues.apache.org/jira/browse/RANGER-4489 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > 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 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (RANGER-4480) Pagination with default pageSize gets applied, even when pagination param pageSize is absent
[ https://issues.apache.org/jira/browse/RANGER-4480 ] Prashant Satam deleted comment on RANGER-4480: was (Author: JIRAUSER300185): Apache Review Request -> https://reviews.apache.org/r/74681/ > Pagination with default pageSize gets applied, even when pagination param > pageSize is absent > > > 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)
[jira] [Commented] (RANGER-4491) Need new API for DataShare in Dataset Summary
[ https://issues.apache.org/jira/browse/RANGER-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783251#comment-17783251 ] Prashant Satam commented on RANGER-4491: This is a duplicate Ticket > Need new API for DataShare in Dataset Summary > -- > > Key: RANGER-4491 > URL: https://issues.apache.org/jira/browse/RANGER-4491 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Prashant Satam >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4448) GDS CRUD APIs should return proper response and message in case of failure
[
https://issues.apache.org/jira/browse/RANGER-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4448:
---
Description:
Description: We need to handle following cases and return proper error message
and response: # In many cases 400 or 500 is thrown, in case the use does not
have permissions to execute the API. We need to handle such cases and throw 403
and return proper error message.
# In case where user is trying to enter duplicate records, the error is thrown
with SQL query in response. In such cases, we need to throw 400 and return
proper error message.
Example :
1)On the POST API call /service/gds/resource with duplicate resources following
error is thrown:
{code:java}
{"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.7.12.v20230209-e5c4074ef3):
org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
(data_share_id, resource_signature)=(3,
c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
data_share_id, description, guid, is_enabled, name, options, profiles,
resource, resource_signature, row_filter, sub_resource_masks,
sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters bound]"}
{code}
We need to catch such exception in create API calls and return proper response.
was:
In case of GDS APIs the responses are improper for error requests
Some cases have improper errorCodes where expected ErrorCodes is 403 we get
400,500 in response
Example :
1)On the POST API call /service/gds/resource with duplicate resources following
error is thrown:
{code:java}
{"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.7.12.v20230209-e5c4074ef3):
org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
(data_share_id, resource_signature)=(3,
c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
data_share_id, description, guid, is_enabled, name, options, profiles,
resource, resource_signature, row_filter, sub_resource_masks,
sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters bound]"}
{code}
We need to catch such exception in create API calls and return proper response.
> GDS CRUD APIs should return proper response and message in case of failure
> --
>
> Key: RANGER-4448
> URL: https://issues.apache.org/jira/browse/RANGER-4448
> Project: Ranger
> Issue Type: Sub-task
> Components: admin
>Reporter: Subhrat Chaudhary
>Assignee: Prashant Satam
>Priority: Major
>
> Description: We need to handle following cases and return proper error
> message and response: # In many cases 400 or 500 is thrown, in case the use
> does not have permissions to execute the API. We need to handle such cases
> and throw 403 and return proper error message.
> # In case where user is trying to enter duplicate records, the error is
> thrown with SQL query in response. In such cases, we need to throw 400 and
> return proper error message.
>
> Example :
> 1)On the POST API call /service/gds/resource with duplicate resources
> following error is thrown:
> {code:java}
> {"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
> org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
> constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
> (data_share_id, resource_signature)=(3,
> c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
> exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
> access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
> data_share_id, description, guid, is_enabled, name, options, profiles,
> resource, resource_signature, row_filter, sub_resource_masks,
> sub_resource_names, UPDATE_TIME, UPD_BY_ID,
[jira] [Updated] (RANGER-4448) GDS CRUD APIs should return proper response and message in case of failure
[
https://issues.apache.org/jira/browse/RANGER-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4448:
---
Summary: GDS CRUD APIs should return proper response and message in case of
failure (was: Handle GDS APIs with appropriate response in case of error in
request)
> GDS CRUD APIs should return proper response and message in case of failure
> --
>
> Key: RANGER-4448
> URL: https://issues.apache.org/jira/browse/RANGER-4448
> Project: Ranger
> Issue Type: Sub-task
> Components: admin
>Reporter: Subhrat Chaudhary
>Assignee: Prashant Satam
>Priority: Major
>
> In case of GDS APIs the responses are improper for error requests
> Some cases have improper errorCodes where expected ErrorCodes is 403 we get
> 400,500 in response
>
> Example :
> 1)On the POST API call /service/gds/resource with duplicate resources
> following error is thrown:
> {code:java}
> {"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
> org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
> constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
> (data_share_id, resource_signature)=(3,
> c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
> exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
> access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
> data_share_id, description, guid, is_enabled, name, options, profiles,
> resource, resource_signature, row_filter, sub_resource_masks,
> sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters
> bound]"} {code}
> We need to catch such exception in create API calls and return proper
> response.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of error in request
[
https://issues.apache.org/jira/browse/RANGER-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4448:
---
Description:
In case of GDS APIs the responses are improper for error requests
Some cases have improper errorCodes where expected ErrorCodes is 403 we get
400,500 in response
Example :
1)On the POST API call /service/gds/resource with duplicate resources following
error is thrown:
{code:java}
{"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.7.12.v20230209-e5c4074ef3):
org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
(data_share_id, resource_signature)=(3,
c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
data_share_id, description, guid, is_enabled, name, options, profiles,
resource, resource_signature, row_filter, sub_resource_masks,
sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters bound]"}
{code}
We need to catch such exception in create API calls and return proper response.
was:
In case of GDS APIs the responses are improper for error requests
Example :
1)On the POST API call /service/gds/resource with duplicate resources following
error is thrown:
{code:java}
{"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.7.12.v20230209-e5c4074ef3):
org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
(data_share_id, resource_signature)=(3,
c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
data_share_id, description, guid, is_enabled, name, options, profiles,
resource, resource_signature, row_filter, sub_resource_masks,
sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters bound]"}
{code}
We need to catch such exception in create API calls and return proper response.
> Handle GDS APIs with appropriate response in case of error in request
> -
>
> Key: RANGER-4448
> URL: https://issues.apache.org/jira/browse/RANGER-4448
> Project: Ranger
> Issue Type: Sub-task
> Components: admin
>Reporter: Subhrat Chaudhary
>Assignee: Prashant Satam
>Priority: Major
>
> In case of GDS APIs the responses are improper for error requests
> Some cases have improper errorCodes where expected ErrorCodes is 403 we get
> 400,500 in response
>
> Example :
> 1)On the POST API call /service/gds/resource with duplicate resources
> following error is thrown:
> {code:java}
> {"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
> org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
> constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
> (data_share_id, resource_signature)=(3,
> c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
> exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
> access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
> data_share_id, description, guid, is_enabled, name, options, profiles,
> resource, resource_signature, row_filter, sub_resource_masks,
> sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters
> bound]"} {code}
> We need to catch such exception in create API calls and return proper
> response.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of error in request
[
https://issues.apache.org/jira/browse/RANGER-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4448:
---
Description:
In case of GDS APIs the responses are improper for error requests
Example :
1)On the POST API call /service/gds/resource with duplicate resources following
error is thrown:
{code:java}
{"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.7.12.v20230209-e5c4074ef3):
org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
(data_share_id, resource_signature)=(3,
c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
data_share_id, description, guid, is_enabled, name, options, profiles,
resource, resource_signature, row_filter, sub_resource_masks,
sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters bound]"}
{code}
We need to catch such exception in create API calls and return proper response.
was:
In case of GDS APIs the responses are not proper for error requests
On the POST API call /service/gds/resource with duplicate ID following error is
thrown:
{code:java}
{"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.7.12.v20230209-e5c4074ef3):
org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
(data_share_id, resource_signature)=(3,
c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
data_share_id, description, guid, is_enabled, name, options, profiles,
resource, resource_signature, row_filter, sub_resource_masks,
sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters bound]"}
{code}
We need to catch such exception in create API calls and return proper response.
> Handle GDS APIs with appropriate response in case of error in request
> -
>
> Key: RANGER-4448
> URL: https://issues.apache.org/jira/browse/RANGER-4448
> Project: Ranger
> Issue Type: Sub-task
> Components: admin
>Reporter: Subhrat Chaudhary
>Assignee: Prashant Satam
>Priority: Major
>
> In case of GDS APIs the responses are improper for error requests
>
> Example :
> 1)On the POST API call /service/gds/resource with duplicate resources
> following error is thrown:
> {code:java}
> {"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
> org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
> constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
> (data_share_id, resource_signature)=(3,
> c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
> exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
> access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
> data_share_id, description, guid, is_enabled, name, options, profiles,
> resource, resource_signature, row_filter, sub_resource_masks,
> sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters
> bound]"} {code}
> We need to catch such exception in create API calls and return proper
> response.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4514) Sort params are interchanged in GDS API response
[ https://issues.apache.org/jira/browse/RANGER-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4514: -- Assignee: Prashant Satam Patch in Review > [https://reviews.apache.org/r/74719/diff/1#index_header] > Sort params are interchanged in GDS API response > > > Key: RANGER-4514 > URL: https://issues.apache.org/jira/browse/RANGER-4514 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Prashant Satam >Assignee: Prashant Satam >Priority: Major > > The values of sort parameters sortBy and sortType are interchanged in the > response received for the GDS APIs. > Steps to reproduce: > * Create 2 datasets > * Fetch them using GET API - /service/gds/dataset?sortBy=id=ASC > * Expected: in response the sort params: sortBy=id, sortType=ASC > * Actual response: sort params: sortBy=ASC, sortType=id -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of error in request
[
https://issues.apache.org/jira/browse/RANGER-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Satam updated RANGER-4448:
---
Summary: Handle GDS APIs with appropriate response in case of error in
request (was: Handle GDS APIs with appropriate response in case of errors in
request)
> Handle GDS APIs with appropriate response in case of error in request
> -
>
> Key: RANGER-4448
> URL: https://issues.apache.org/jira/browse/RANGER-4448
> Project: Ranger
> Issue Type: Sub-task
> Components: admin
>Reporter: Subhrat Chaudhary
>Assignee: Prashant Satam
>Priority: Major
>
> In case of GDS APIs the responses are not proper for error requests
>
>
> On the POST API call /service/gds/resource with duplicate ID following error
> is thrown:
>
> {code:java}
> {"statusCode": 1,"msgDesc": "Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.7.12.v20230209-e5c4074ef3):
> org.eclipse.persistence.exceptions.DatabaseException\nInternal Exception:
> org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique
> constraint \"x_gds_shared_resource_uk_resource_signature\"\n Detail: Key
> (data_share_id, resource_signature)=(3,
> c5bd97fc0b8eaeb302f7498693f509178a134534cf7eb46d9edd55de71f7ab6c) already
> exists.\nError Code: 0\nCall: INSERT INTO x_gds_shared_resource (id,
> access_types, ADDED_BY_ID, additional_info, condition_expr, CREATE_TIME,
> data_share_id, description, guid, is_enabled, name, options, profiles,
> resource, resource_signature, row_filter, sub_resource_masks,
> sub_resource_names, UPDATE_TIME, UPD_BY_ID, version) VALUES (?, ?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)\n\tbind => [21 parameters
> bound]"} {code}
> We need to catch such exception in create API calls and return proper
> response.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
