[jira] [Created] (RANGER-4428) Need a new API to get list of services mapped to a zone
Subhrat Chaudhary created RANGER-4428:
-
Summary: Need a new API to get list of services mapped to a zone
Key: RANGER-4428
URL: https://issues.apache.org/jira/browse/RANGER-4428
Project: Ranger
Issue Type: Sub-task
Components: admin
Reporter: Subhrat Chaudhary
Need a new API to get list of services mapped to a zone for the Create
Datashare >> Step 2 > Select Security Zone >> Select Service
Request: zoneId will received in params
Response: {color:#00}Map{color}
{color:#00}If no zone-id/name is specified should get all the service with
atlease one zone (zoneless service should not be returned){color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4428) Need a new API to get list of zones mapped to a service
[
https://issues.apache.org/jira/browse/RANGER-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subhrat Chaudhary updated RANGER-4428:
--
Summary: Need a new API to get list of zones mapped to a service (was:
Need a new API to get list of services mapped to a zone)
> Need a new API to get list of zones mapped to a service
> ---
>
> Key: RANGER-4428
> URL: https://issues.apache.org/jira/browse/RANGER-4428
> Project: Ranger
> Issue Type: Sub-task
> Components: admin
>Reporter: Subhrat Chaudhary
>Priority: Major
>
> Need a new API to get list of services mapped to a zone for the Create
> Datashare >> Step 2 > Select Security Zone >> Select Service
> Request: zoneId will received in params
> Response: {color:#00}Map{color}
> {color:#00}If no zone-id/name is specified should get all the service
> with atlease one zone (zoneless service should not be returned){color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4428) Need a new API to get list of zones mapped to a service
[
https://issues.apache.org/jira/browse/RANGER-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subhrat Chaudhary updated RANGER-4428:
--
Description:
Need a new API to get list of zones mapped to a service for the Create
Datashare >> Step 2 > Select Service >> Select Zone
Request: serviceId will received in params
Response: {color:#00}Map{color}
was:
Need a new API to get list of services mapped to a zone for the Create
Datashare >> Step 2 > Select Security Zone >> Select Service
Request: zoneId will received in params
Response: {color:#00}Map{color}
{color:#00}If no zone-id/name is specified should get all the service with
atlease one zone (zoneless service should not be returned){color}
> Need a new API to get list of zones mapped to a service
> ---
>
> Key: RANGER-4428
> URL: https://issues.apache.org/jira/browse/RANGER-4428
> Project: Ranger
> Issue Type: Sub-task
> Components: admin
>Reporter: Subhrat Chaudhary
>Priority: Major
>
> Need a new API to get list of zones mapped to a service for the Create
> Datashare >> Step 2 > Select Service >> Select Zone
> Request: serviceId will received in params
> Response: {color:#00}Map{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Review Request 74602: RANGER:4408 : Get DataShares linked to Dataset
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74602/
---
(Updated Sept. 25, 2023, 7:46 a.m.)
Review request for ranger, Anand Nadar, Madhan Neethiraj, and Subhrat Chaudhary.
Bugs: RANGER-4408
https://issues.apache.org/jira/browse/RANGER-4408
Repository: ranger
Description
---
Get dataShares that are Linked to specfic Dataset
Diffs (updated)
-
agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java
440bb4c24
security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java d2bd0789d
security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java
059954b46
security-admin/src/main/java/org/apache/ranger/db/XXGdsDataShareInDatasetDao.java
52c441104
security-admin/src/main/java/org/apache/ranger/db/XXGdsSharedResourceDao.java
d3bd4d65b
security-admin/src/main/java/org/apache/ranger/rest/GdsREST.java 653e397d4
security-admin/src/main/java/org/apache/ranger/security/context/RangerAPIList.java
de9014072
security-admin/src/main/java/org/apache/ranger/view/RangerDataShareInfo.java
PRE-CREATION
Diff: https://reviews.apache.org/r/74602/diff/2/
Changes: https://reviews.apache.org/r/74602/diff/1-2/
Testing (updated)
---
Add a dataset then link dataShares to a dataset you will get list of dataShares
that are linked to the datasetId mentioned . API (/datashares/dataset).Need to
send Query Param as dataShareHeader=false
Other query params =
dataShareHeader=false&datasetId=1&sortBy=createTime&sortType=desc&pageSize=1
Response===>
{
"isEnabled": true,
"dataShareId": 1,
"dataShareRequestId": 1,
"serviceName": "Resource_policy_Performance_test_50K",
"zoneName": "Gds_Security_Zone",
"resourceCount": 4,
"gdsSharedStatus": "REQUESTED",
"name": "RangerDataShare12",
"description": "This is RangerDatashare"
}
Thanks,
Prashant Satam
Re: Review Request 74594: RANGER:4397 : API to get DataShare id, name List
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74594/
---
(Updated Sept. 25, 2023, 7:52 a.m.)
Review request for ranger, Anand Nadar, Madhan Neethiraj, and Subhrat Chaudhary.
Bugs: RANGER-4397
https://issues.apache.org/jira/browse/RANGER-4397
Repository: ranger
Description (updated)
---
API to fetch List of datashare
Diffs (updated)
-
agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java
440bb4c24
security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java d2bd0789d
security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java
059954b46
security-admin/src/main/java/org/apache/ranger/db/XXGdsDataShareInDatasetDao.java
52c441104
security-admin/src/main/java/org/apache/ranger/db/XXGdsSharedResourceDao.java
d3bd4d65b
security-admin/src/main/java/org/apache/ranger/rest/GdsREST.java 653e397d4
security-admin/src/main/java/org/apache/ranger/security/context/RangerAPIList.java
de9014072
security-admin/src/main/java/org/apache/ranger/view/RangerDataShareInfo.java
PRE-CREATION
Diff: https://reviews.apache.org/r/74594/diff/2/
Changes: https://reviews.apache.org/r/74594/diff/1-2/
Testing (updated)
---
Add multiple datashares then will able to fetch list of dataShares
API (/datashares/dataset).Need to send Query Param as dataShareHeader=true
Other query params =
dataShareHeader=false&datasetId=1&sortBy=createTime&sortType=desc&pageSize=1
Response=>
{
"isEnabled": true,
"dataShareId": 2,
"name": "RangerDataShare1",
"description": "This is RangerDatashare"
}
Thanks,
Prashant Satam
[jira] [Commented] (RANGER-4418) Upgrade hadoop version and use shaded hadoop client artifacts
[
https://issues.apache.org/jira/browse/RANGER-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768603#comment-17768603
]
Bhavik Patel commented on RANGER-4418:
--
[~eub] Thanks for working this.
Any specific reason to use hadoop-3.3.4? Can you upgrade hadoop-3.3.6 as it
looks like more stable.
> Upgrade hadoop version and use shaded hadoop client artifacts
> -
>
> Key: RANGER-4418
> URL: https://issues.apache.org/jira/browse/RANGER-4418
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 2.3.0, 2.4.0
>Reporter: YUBI LEE
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - Upgrade the hadoop version Ranger uses.
> - Try to use shaded hadoop client artifacts if possible.
> Related issue: https://issues.apache.org/jira/browse/HADOOP-11804
> If shaded hadoop client artifacts ({{hadoop-client-api}},
> {{hadoop-client-runtime}}) are used, Ranger will be free to use any version
> of thirdparty libraries without collision.
> I will make a pull request soon.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4389) extend ABAC to use few internal attributes of users and groups, like syncSource, isInternal, emailAddress
[ https://issues.apache.org/jira/browse/RANGER-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768626#comment-17768626 ] Himanshu Maurya commented on RANGER-4389: - Hi [~madhan] Can you kindly share some wiki/blogs related to this feature? Thankyou > extend ABAC to use few internal attributes of users and groups, like > syncSource, isInternal, emailAddress > - > > Key: RANGER-4389 > URL: https://issues.apache.org/jira/browse/RANGER-4389 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-4389.patch > > > Ranger ABAC allows access/masking/row-filtering policies to be setup based on > attributes of users and groups. It will help to make following internal > attributes available for use in ABAC policies: > * syncSource > * isInternal > * emailAddress > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4389) extend ABAC to use few internal attributes of users and groups, like syncSource, isInternal, emailAddress
[ https://issues.apache.org/jira/browse/RANGER-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768626#comment-17768626 ] Himanshu Maurya edited comment on RANGER-4389 at 9/25/23 10:39 AM: --- Hi [~madhan] , [~barbara] Can you kindly share some wiki/blogs related to this feature? Thankyou was (Author: JIRAUSER298460): Hi [~madhan] Can you kindly share some wiki/blogs related to this feature? Thankyou > extend ABAC to use few internal attributes of users and groups, like > syncSource, isInternal, emailAddress > - > > Key: RANGER-4389 > URL: https://issues.apache.org/jira/browse/RANGER-4389 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-4389.patch > > > Ranger ABAC allows access/masking/row-filtering policies to be setup based on > attributes of users and groups. It will help to make following internal > attributes available for use in ABAC policies: > * syncSource > * isInternal > * emailAddress > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4429) Pagination not working for Securityzones API
Prashant Satam created RANGER-4429: -- Summary: Pagination not working for Securityzones API Key: RANGER-4429 URL: https://issues.apache.org/jira/browse/RANGER-4429 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Prashant Satam -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4429) Pagination not working for Securityzones API
[ https://issues.apache.org/jira/browse/RANGER-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prashant Satam reassigned RANGER-4429: -- Assignee: Prashant Satam > Pagination not working for Securityzones API > > > Key: RANGER-4429 > URL: https://issues.apache.org/jira/browse/RANGER-4429 > 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-4430) Create datshare and sharedResource in cascade
Subhrat Chaudhary created RANGER-4430: - Summary: Create datshare and sharedResource in cascade Key: RANGER-4430 URL: https://issues.apache.org/jira/browse/RANGER-4430 Project: Ranger Issue Type: Sub-task Components: admin Reporter: Subhrat Chaudhary Currently we have separate APIs to create Datashare and SharedResource. We need a single API to receive custom object with datashare and mapped sharedResources. We need to first create datashare and created sharedResources with id of the newly created datashare. This has to be done in a transaction. Created datashare will have ACL with ADMIN permission for the creating user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4431) Need additional filters for GET sharedResources API
Subhrat Chaudhary created RANGER-4431:
-
Summary: Need additional filters for GET sharedResources API
Key: RANGER-4431
URL: https://issues.apache.org/jira/browse/RANGER-4431
Project: Ranger
Issue Type: Sub-task
Components: admin
Reporter: Subhrat Chaudhary
{color:#00}Need additional filters for GET sharedResources API -
/gds/resource
{color}
{color:#00}Filter: sharedResourceName - partial search, resourceName
{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4431) Need additional filters for GET sharedResources API
[
https://issues.apache.org/jira/browse/RANGER-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subhrat Chaudhary updated RANGER-4431:
--
Description:
{color:#00}Need additional filters for GET sharedResources API -
/gds/resource{color}
{color:#00}Filter: sharedResourceName, resourceName - partial search
{color}
was:
{color:#00}Need additional filters for GET sharedResources API -
/gds/resource
{color}
{color:#00}Filter: sharedResourceName - partial search, resourceName
{color}
> Need additional filters for GET sharedResources API
> ---
>
> Key: RANGER-4431
> URL: https://issues.apache.org/jira/browse/RANGER-4431
> Project: Ranger
> Issue Type: Sub-task
> Components: admin
>Reporter: Subhrat Chaudhary
>Priority: Major
>
> {color:#00}Need additional filters for GET sharedResources API -
> /gds/resource{color}
> {color:#00}Filter: sharedResourceName, resourceName - partial search
> {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4383) In Audit, Plugin Status tab if the record of respective service is in second page then Service Type filter for that service would show no result
[ https://issues.apache.org/jira/browse/RANGER-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768717#comment-17768717 ] Dhaval Shah commented on RANGER-4383: - Hi , Committted in master branch : https://github.com/apache/ranger/commit/622a1dacbdd39ec08783fd3d411bedb66f1407b1 Thanks > In Audit, Plugin Status tab if the record of respective service is in second > page then Service Type filter for that service would show no result > > > Key: RANGER-4383 > URL: https://issues.apache.org/jira/browse/RANGER-4383 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4383.patch > > > In Audit, Plugin Status tab if the records of respective service for eg KMS > is in second page then Service Type filter for that service would show no > result. > Workaround is using Service Name filter. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4381) [Ranger React UI] Difference in user lookup API request in permissions module page between React UI and BackBone UI
[ https://issues.apache.org/jira/browse/RANGER-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768718#comment-17768718 ] Dhaval Shah commented on RANGER-4381: - Hi, Committed in master branch : https://github.com/apache/ranger/commit/6b3bd1c85ccb5ed2c13e398e118c65484f92be58 Thanks > [Ranger React UI] Difference in user lookup API request in permissions module > page between React UI and BackBone UI > --- > > Key: RANGER-4381 > URL: https://issues.apache.org/jira/browse/RANGER-4381 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4381.patch, 0002-RANGER-4381.patch, > 0003-RANGER-4381.patch, 0004-RANGER-4381.patch > > > In Ranger backbone UI, when trying to add users to a particular permissions > module, > when typing the user name, the user lookup is done only for users who are > visible. > In React UI, the lookup is not being restricted to visible users. > Ideally, if a user is hidden, it would mean that the user is deleted from the > source, > and in such scenarios, the users must not be listed for user lookups. > This is a regression from the previous UI behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4358) Keep the usersync details popup names same as the backbone js names
[
https://issues.apache.org/jira/browse/RANGER-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768720#comment-17768720
]
Dhaval Shah commented on RANGER-4358:
-
Hi,
Committed in master branch :
https://github.com/apache/ranger/commit/f740ad33208618fd47f5d2b314c4978300cbd7c2
Thanks
> Keep the usersync details popup names same as the backbone js names
> ---
>
> Key: RANGER-4358
> URL: https://issues.apache.org/jira/browse/RANGER-4358
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
> Labels: ranger-react
> Fix For: 3.0.0
>
>
> {color:#172b4d}The data field names are different in the usersync audits sync
> details popup in ReactJS when compared to backbone JS.{color}
> {color:#172b4d}Ideally, both of them should be the same and the field names
> in React JS should be the same as in BackBone JS.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4407) Add server side validation for service audit filter
[ https://issues.apache.org/jira/browse/RANGER-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768719#comment-17768719 ] Dhaval Shah commented on RANGER-4407: - Hi , Committed in master branch : https://github.com/apache/ranger/commit/0f70a24f45b394043239d1898d7276b67400bfd2 Thanks > Add server side validation for service audit filter > --- > > Key: RANGER-4407 > URL: https://issues.apache.org/jira/browse/RANGER-4407 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Mugdha Varadkar >Assignee: Dineshkumar Yadav >Priority: Major > Labels: ranger-react > > This jira is tracking two fixes : > 1) Add Server side validation for service audit filters at the time of create > / edit service > 2) Add UI side fix to catch any error while parsing the service audit filters > without breaking the page -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4383) In Audit, Plugin Status tab if the record of respective service is in second page then Service Type filter for that service would show no result
[ https://issues.apache.org/jira/browse/RANGER-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768721#comment-17768721 ] Brijesh Bhalala commented on RANGER-4383: - commited to [Apache master|https://github.com/apache/ranger/commit/622a1dacbdd39ec08783fd3d411bedb66f1407b1] branch > In Audit, Plugin Status tab if the record of respective service is in second > page then Service Type filter for that service would show no result > > > Key: RANGER-4383 > URL: https://issues.apache.org/jira/browse/RANGER-4383 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4383.patch > > > In Audit, Plugin Status tab if the records of respective service for eg KMS > is in second page then Service Type filter for that service would show no > result. > Workaround is using Service Name filter. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4381) [Ranger React UI] Difference in user lookup API request in permissions module page between React UI and BackBone UI
[ https://issues.apache.org/jira/browse/RANGER-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768722#comment-17768722 ] Brijesh Bhalala commented on RANGER-4381: - commited to [Apache master|https://github.com/apache/ranger/commit/6b3bd1c85ccb5ed2c13e398e118c65484f92be58] branch > [Ranger React UI] Difference in user lookup API request in permissions module > page between React UI and BackBone UI > --- > > Key: RANGER-4381 > URL: https://issues.apache.org/jira/browse/RANGER-4381 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4381.patch, 0002-RANGER-4381.patch, > 0003-RANGER-4381.patch, 0004-RANGER-4381.patch > > > In Ranger backbone UI, when trying to add users to a particular permissions > module, > when typing the user name, the user lookup is done only for users who are > visible. > In React UI, the lookup is not being restricted to visible users. > Ideally, if a user is hidden, it would mean that the user is deleted from the > source, > and in such scenarios, the users must not be listed for user lookups. > This is a regression from the previous UI behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4407) Add server side validation for service audit filter
[ https://issues.apache.org/jira/browse/RANGER-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dineshkumar Yadav resolved RANGER-4407. --- Fix Version/s: 3.0.0 Resolution: Fixed > Add server side validation for service audit filter > --- > > Key: RANGER-4407 > URL: https://issues.apache.org/jira/browse/RANGER-4407 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Mugdha Varadkar >Assignee: Dineshkumar Yadav >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > > This jira is tracking two fixes : > 1) Add Server side validation for service audit filters at the time of create > / edit service > 2) Add UI side fix to catch any error while parsing the service audit filters > without breaking the page -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74609: RANGER-4234
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74609/ --- (Updated Sept. 25, 2023, 7:02 p.m.) Review request for ranger and madhan. Changes --- version 6 includes changes to RangerRequestScriptEvaluator, which were inadvertently left out of the most recent patch (for which I apologize abjectly!). It was made by cloning the current version of origin/master, making that one change, and generating a patch. Repository: ranger Description --- RANGER-4234: Eliminate need for splitting delimited strings into arrays in policy conditions Diffs (updated) - agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerRequestScriptEvaluator.java 7ac20764f Diff: https://reviews.apache.org/r/74609/diff/6/ Changes: https://reviews.apache.org/r/74609/diff/5-6/ Testing --- File Attachments 0001-RANGER-4234.patch https://reviews.apache.org/media/uploaded/files/2023/09/22/19380bc1-e7ad-4fab-880d-324e38783c05__0001-RANGER-4234.patch RANGER-4234.patch https://reviews.apache.org/media/uploaded/files/2023/09/22/0f300895-c3a6-4dbd-8bd3-23dc1d6e3b49__RANGER-4234.patch Thanks, Barbara Eckman
Re: Review Request 74609: RANGER-4234
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74609/ --- (Updated Sept. 25, 2023, 7:34 p.m.) Review request for ranger and madhan. Changes --- added JsvaScriptEdits import to RangerRequestScriptEvaluator Repository: ranger Description --- RANGER-4234: Eliminate need for splitting delimited strings into arrays in policy conditions Diffs (updated) - agents-common/dev-support/spotbugsIncludeFile.xml PRE-CREATION agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerRequestScriptEvaluator.java 7ac20764f Diff: https://reviews.apache.org/r/74609/diff/7/ Changes: https://reviews.apache.org/r/74609/diff/6-7/ Testing --- File Attachments 0001-RANGER-4234.patch https://reviews.apache.org/media/uploaded/files/2023/09/22/19380bc1-e7ad-4fab-880d-324e38783c05__0001-RANGER-4234.patch RANGER-4234.patch https://reviews.apache.org/media/uploaded/files/2023/09/22/0f300895-c3a6-4dbd-8bd3-23dc1d6e3b49__RANGER-4234.patch Thanks, Barbara Eckman
[jira] [Commented] (RANGER-4418) Upgrade hadoop version and use shaded hadoop client artifacts
[
https://issues.apache.org/jira/browse/RANGER-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768951#comment-17768951
]
YUBI LEE commented on RANGER-4418:
--
[~bpatel] Thanks for reply. I changed the version from 3.3.4 to 3.3.6.
> Upgrade hadoop version and use shaded hadoop client artifacts
> -
>
> Key: RANGER-4418
> URL: https://issues.apache.org/jira/browse/RANGER-4418
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 2.3.0, 2.4.0
>Reporter: YUBI LEE
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> - Upgrade the hadoop version Ranger uses.
> - Try to use shaded hadoop client artifacts if possible.
> Related issue: https://issues.apache.org/jira/browse/HADOOP-11804
> If shaded hadoop client artifacts ({{hadoop-client-api}},
> {{hadoop-client-runtime}}) are used, Ranger will be free to use any version
> of thirdparty libraries without collision.
> I will make a pull request soon.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4426) Add field approver in dataset request entities
[ https://issues.apache.org/jira/browse/RANGER-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subhrat Chaudhary reassigned RANGER-4426: - Assignee: Subhrat Chaudhary > Add field approver in dataset request entities > -- > > Key: RANGER-4426 > URL: https://issues.apache.org/jira/browse/RANGER-4426 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Subhrat Chaudhary >Assignee: Subhrat Chaudhary >Priority: Major > > To be able to record details of the approver of the requests i.e. request to > add datashare in dataset and request to add dataset in project. we need an > approver field in RangerDatashareInDataset and RangerDatasetInProject. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74621: RANGER-4426: Add approver in GDS request entities
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74621/ --- Review request for ranger, Anand Nadar, Madhan Neethiraj, Monika Kachhadiya, and Prashant Satam. Bugs: https://issues.apache.org/jira/browse/RANGER-4426 https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/RANGER-4426 Repository: ranger Description --- To be able to record details of the approver of the requests i.e. request to add datashare in dataset and request to add dataset in project. we need an approver field in RangerDatashareInDataset and RangerDatasetInProject. Diffs - agents-common/src/main/java/org/apache/ranger/plugin/model/RangerGds.java a1c883356 security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 424f38d9e security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 5ffa23f33 security-admin/src/main/java/org/apache/ranger/entity/XXGdsDataShareInDataset.java 8c59e0898 security-admin/src/main/java/org/apache/ranger/entity/XXGdsDatasetInProject.java 6babde527 security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareInDatasetService.java d32282c27 security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetInProjectService.java 0ed51c249 Diff: https://reviews.apache.org/r/74621/diff/1/ Testing --- Validations done: 1. Added approver in POST API /gds/datashare/dataset, on GET API response approver is updated. The approver value is updated in the table x_gds_data_share_in_dataset, for the record inserted. 2. Added approver in POST API /gds/dataset/project, on GET API response approver is updated. The approver value is updated in the table x_gds_data_share_in_dataset, for the record inserted. Thanks, Subhrat Chaudhary
Re: Review Request 74621: RANGER-4426: Add approver in GDS request entities
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74621/ --- (Updated Sept. 26, 2023, 9:53 a.m.) Review request for ranger, Anand Nadar, Madhan Neethiraj, Monika Kachhadiya, and Prashant Satam. Bugs: https://issues.apache.org/jira/browse/RANGER-4426 https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/RANGER-4426 Repository: ranger Description --- To be able to record details of the approver of the requests i.e. request to add datashare in dataset and request to add dataset in project. we need an approver field in RangerDatashareInDataset and RangerDatasetInProject. Diffs (updated) - agents-common/src/main/java/org/apache/ranger/plugin/model/RangerGds.java a1c883356 security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 424f38d9e security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 5ffa23f33 security-admin/src/main/java/org/apache/ranger/entity/XXGdsDataShareInDataset.java 8c59e0898 security-admin/src/main/java/org/apache/ranger/entity/XXGdsDatasetInProject.java 6babde527 security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareInDatasetService.java d32282c27 security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetInProjectService.java 0ed51c249 Diff: https://reviews.apache.org/r/74621/diff/2/ Changes: https://reviews.apache.org/r/74621/diff/1-2/ Testing --- Validations done: 1. Added approver in POST API /gds/datashare/dataset, on GET API response approver is updated. The approver value is updated in the table x_gds_data_share_in_dataset, for the record inserted. 2. Added approver in POST API /gds/dataset/project, on GET API response approver is updated. The approver value is updated in the table x_gds_data_share_in_dataset, for the record inserted. Thanks, Subhrat Chaudhary
