date:20231106

Re: Review Request 74720: RANGER-4283: [WIP] UI for GDS: UI Design changes for add principal, internal tab listing and CSS changes

2023-11-06 Thread Anand Nadar


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

(Updated Nov. 7, 2023, 7:36 a.m.)


Review request for ranger, Ankita Sinha, Brijesh Bhalala, Dhaval Rajpara, 
Madhan Neethiraj, Mugdha Varadkar, Prashant Satam, and Subhrat Chaudhary.


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

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/RANGER-4283


Repository: ranger


Description
---

UI Design changes for add principal, internal tab listing and CSS changes


Diffs
-

  security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx 
98495f6cc 
  security-admin/src/main/webapp/react-webapp/src/styles/style.css 7cb54b7dc 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/AccessGrantForm.jsx
 32c48046c 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/AddDatasetView.jsx
 b337ce009 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetDetailFullView.jsx
 25f830443 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetDetailLayout.jsx
 779ab523b 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetPolicyItemComp.jsx
 6bc775143 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatashareInDatasetListComp.jsx
 PRE-CREATION 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/MyDatasetListing.jsx
 3bf4347cd 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/PrinciplePermissionComp.jsx
 d0b8fadf7 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/AddDatashareView.jsx
 57194742d 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/AddSharedResourceComp.jsx
 b6cc774ef 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/DatashareDetailFullView.jsx
 a315de5e1 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/DatashareDetailLayout.jsx
 c0c52aea6 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/MyDatashareListing.jsx
 cef56559c 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Request/RequestDetailView.jsx
 d6bfe7cf4 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Request/RequestListing.jsx
 60b96699f 


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


Testing (updated)
---

Validated dataset/datashare listing with sorting by datasetName and 
datashareName
Validated shared resource listing, add/edit/delete of shared resource after new 
UI design.
Validated internal datashare listing tab of dataset detail view for new UI 
design.
Validated add principal changes after new UI design.
Validated dependant service and zone selection in datashare creation.


Thanks,

Anand Nadar

Re: Review Request 74720: RANGER-4283: [WIP] UI for GDS: UI Design changes for add principal, internal tab listing and CSS changes

2023-11-06 Thread Anand Nadar


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

(Updated Nov. 7, 2023, 7:36 a.m.)


Review request for ranger, Ankita Sinha, Brijesh Bhalala, Dhaval Rajpara, 
Madhan Neethiraj, Mugdha Varadkar, Prashant Satam, and Subhrat Chaudhary.


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

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/RANGER-4283


Repository: ranger


Description
---

UI Design changes for add principal, internal tab listing and CSS changes


Diffs
-

  security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx 
98495f6cc 
  security-admin/src/main/webapp/react-webapp/src/styles/style.css 7cb54b7dc 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/AccessGrantForm.jsx
 32c48046c 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/AddDatasetView.jsx
 b337ce009 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetDetailFullView.jsx
 25f830443 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetDetailLayout.jsx
 779ab523b 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetPolicyItemComp.jsx
 6bc775143 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatashareInDatasetListComp.jsx
 PRE-CREATION 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/MyDatasetListing.jsx
 3bf4347cd 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/PrinciplePermissionComp.jsx
 d0b8fadf7 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/AddDatashareView.jsx
 57194742d 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/AddSharedResourceComp.jsx
 b6cc774ef 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/DatashareDetailFullView.jsx
 a315de5e1 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/DatashareDetailLayout.jsx
 c0c52aea6 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/MyDatashareListing.jsx
 cef56559c 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Request/RequestDetailView.jsx
 d6bfe7cf4 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Request/RequestListing.jsx
 60b96699f 


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


Testing (updated)
---

Validated dataset/datashare listing with sorting by datasetName and 
datashareName
Validated shared resource listing, add/edit/delete of shared resource after new 
UI design.
Validated internal datashare listing tab of dataset detail view for new UI 
design.
Validated add principal changes after new UI design.
Validated dependant service and zone in datashare creation.


Thanks,

Anand Nadar

Review Request 74720: RANGER-4283: [WIP] UI for GDS: UI Design changes for add principal, internal tab listing and CSS changes

2023-11-06 Thread Anand Nadar


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

Review request for ranger, Ankita Sinha, Brijesh Bhalala, Dhaval Rajpara, 
Madhan Neethiraj, Mugdha Varadkar, Prashant Satam, and Subhrat Chaudhary.


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

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/RANGER-4283


Repository: ranger


Description
---

UI Design changes for add principal, internal tab listing and CSS changes


Diffs
-

  security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx 
98495f6cc 
  security-admin/src/main/webapp/react-webapp/src/styles/style.css 7cb54b7dc 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/AccessGrantForm.jsx
 32c48046c 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/AddDatasetView.jsx
 b337ce009 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetDetailFullView.jsx
 25f830443 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetDetailLayout.jsx
 779ab523b 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatasetPolicyItemComp.jsx
 6bc775143 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/DatashareInDatasetListComp.jsx
 PRE-CREATION 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/MyDatasetListing.jsx
 3bf4347cd 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Dataset/PrinciplePermissionComp.jsx
 d0b8fadf7 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/AddDatashareView.jsx
 57194742d 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/AddSharedResourceComp.jsx
 b6cc774ef 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/DatashareDetailFullView.jsx
 a315de5e1 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/DatashareDetailLayout.jsx
 c0c52aea6 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Datashare/MyDatashareListing.jsx
 cef56559c 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Request/RequestDetailView.jsx
 d6bfe7cf4 
  
security-admin/src/main/webapp/react-webapp/src/views/GovernedData/Request/RequestListing.jsx
 60b96699f 


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


Testing
---

Validated dataset/datashare listing with sorting by datasetName and 
datashareName
Validated shared resource listing, add/edit/delete of shared resource after new 
UI design.
Validated internal datashare listing tab of dataset detail view for new UI 
design.
Validated add principal changes after new UI design.


Thanks,

Anand Nadar

[jira] (RANGER-4480) Pagination with default pageSize gets applied, even when pagination param pageSize is absent

2023-11-06 Thread Prashant Satam (Jira)



[ 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)

org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizerFactory ClassNotFoundException

2023-11-06 Thread Yi Zheng

Hi,


The problem I’ve encountered is: after “spark-shell” command, when I first 
enter “spark.sql("select * from test.test_3 ").show(false)” command, it throws 
“ERROR session.SessionState: Error setting up authorization: 
java.lang.ClassNotFoundException: 
org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizerFactory

org.apache.hadoop.hive.ql.metadata.HiveException: 
java.lang.ClassNotFoundException: 
org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizerFactory”. 
when I enter “spark.sql("select * from test.test_3 ").show(false)” command for 
the second time, no error is thrown, and correct result is given back. In 
summary, whenever a new spark session is established, the first spark sql 
command always throws the error, while the following spark sql command will 
not. I have a feeling of some configuration is not set correctly but couldn’t 
figure out what the reason might be of this problem.


Below is some background information. Please let me know if additional 
information is needed. Thank you.

Modules and version:

  *   CDH：6.3.2
  *   Zookeeper：
  *   HDFS：
  *   Spark：2.4.0
  *   Yarn：
  *   Hive：2.1.1
  *   Ranger：2.1.0

Complete error message:

[root@poc6-node1 conf]# spark-shell

Setting default log level to "WARN".

To adjust logging level use sc.setLogLevel(newLevel). For SparkR, use 
setLogLevel(newLevel).

23/11/07 11:16:41 WARN cluster.YarnSchedulerBackend$YarnSchedulerEndpoint: 
Attempted to request executors before the AM has registered!

23/11/07 11:16:41 WARN lineage.LineageWriter: Lineage directory 
/var/log/spark/lineage doesn't exist or is not writable. Lineage for this 
application will be disabled.

Spark context Web UI available at http://poc6-node1:4040

Spark context available as 'sc' (master = yarn, app id = 
application_1698718613783_0048).

Spark session available as 'spark'.

Welcome to

    __

 / __/__  ___ _/ /__

_\ \/ _ \/ _ `/ __/  '_/

   /___/ .__/\_,_/_/ /_/\_\   version 2.4.0-cdh6.3.2

  /_/



Using Scala version 2.11.12 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_181)

Type in expressions to have them evaluated.

Type :help for more information.



scala> spark.sql("select * from test.test_3 ").show(false)

23/11/07 11:17:30 WARN lineage.LineageWriter: Lineage directory 
/var/log/spark/lineage doesn't exist or is not writable. Lineage for this 
application will be disabled.

23/11/07 11:17:35 ERROR session.SessionState: Error setting up authorization: 
java.lang.ClassNotFoundException: 
org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizerFactory

org.apache.hadoop.hive.ql.metadata.HiveException: 
java.lang.ClassNotFoundException: 
org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizerFactory

at 
org.apache.hadoop.hive.ql.metadata.HiveUtils.getAuthorizeProviderManager(HiveUtils.java:385)

at 
org.apache.hadoop.hive.ql.session.SessionState.setupAuth(SessionState.java:873)

at 
org.apache.hadoop.hive.ql.session.SessionState.getAuthenticator(SessionState.java:1559)

at 
org.apache.hadoop.hive.ql.session.SessionState.getUserFromAuthenticator(SessionState.java:1239)

at 
org.apache.hadoop.hive.ql.metadata.Table.getEmptyTable(Table.java:181)

at org.apache.hadoop.hive.ql.metadata.Table.(Table.java:123)

at 
org.apache.spark.sql.hive.client.HiveClientImpl$.toHiveTable(HiveClientImpl.scala:927)

at 
org.apache.spark.sql.hive.client.HiveClientImpl$$anonfun$getPartitions$1.apply(HiveClientImpl.scala:670)

at 
org.apache.spark.sql.hive.client.HiveClientImpl$$anonfun$getPartitions$1.apply(HiveClientImpl.scala:669)

at 
org.apache.spark.sql.hive.client.HiveClientImpl$$anonfun$withHiveState$1.apply(HiveClientImpl.scala:283)

at 
org.apache.spark.sql.hive.client.HiveClientImpl.liftedTree1$1(HiveClientImpl.scala:221)

at 
org.apache.spark.sql.hive.client.HiveClientImpl.retryLocked(HiveClientImpl.scala:220)

at 
org.apache.spark.sql.hive.client.HiveClientImpl.withHiveState(HiveClientImpl.scala:266)

at 
org.apache.spark.sql.hive.client.HiveClientImpl.getPartitions(HiveClientImpl.scala:669)

at 
org.apache.spark.sql.hive.client.HiveClient$class.getPartitions(HiveClient.scala:210)

at 
org.apache.spark.sql.hive.client.HiveClientImpl.getPartitions(HiveClientImpl.scala:84)

at 
org.apache.spark.sql.hive.HiveExternalCatalog$$anonfun$listPartitions$1.apply(HiveExternalCatalog.scala:1232)

at 
org.apache.spark.sql.hive.HiveExternalCatalog$$anonfun$listPartitions$1.apply(HiveExternalCatalog.scala:1230)

at 
org.apache.spark.sql.hive.HiveExternalCatalog.withClient(HiveExternalCatalog.scala:99)

at 
org.apache.spark.sql.hive.HiveExternalCatalog.listPartitions(HiveExternalCatalog.scala:1230)

at 
org.apache.spark.sql.catalyst.catalog.ExternalCatalogWithListener.listPartitions(ExternalCatalogWithListener.scala:254)

Re: Review Request 74717: RANGER-4378: removed static PolicyEngine.impliedAccessGrants

2023-11-06 Thread Abhay Kulkarni


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


Ship it!




Ship It!

- Abhay Kulkarni


On Nov. 3, 2023, 3:31 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74717/
> ---
> 
> (Updated Nov. 3, 2023, 3:31 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Abhay Kulkarni, Monika Kachhadiya, 
> Ramesh Mani, Sailaja Polavarapu, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4378
> https://issues.apache.org/jira/browse/RANGER-4378
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Replaced use of PolicyEngine.getImpliedAccessGrants() with call to 
> ServiceDefUtil.getExpandedImpliedGrants(). This eliminates the need for 
> static member PolicyEngine.impliedAccessGrants.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/PolicyEngine.java
>  858c3f542 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerAbstractPolicyItemEvaluator.java
>  a3e3806ec 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerAuditPolicyEvaluator.java
>  9051a8ce4 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
>  bc627adf5 
> 
> 
> Diff: https://reviews.apache.org/r/74717/diff/4/
> 
> 
> Testing
> ---
> 
> - verified that all unit tests passed successfully
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Re: Apply for contributor permissions

2023-11-06 Thread Madhan Neethiraj

Hello,

Thank you for your interest in contributing to Apache Ranger. You now have 
contributor access.

Welcome to Apache Ranger.

Thanks,
Madhan
Apache Ranger PMC




On 11/2/23, 1:59 AM, "╘微笑依舊" <360989...@qq.com.inva 
LID> wrote:


Hi,


I want to contribute to Apache Ranger. Would you please give me the contributor 
permission? My JIRA ID is answerliao.














╘微笑依舊
360989...@qq.com

Re: Review Request 74681: RANGER:4480:Pagination with default pageSize gets applied, even when pagination param pageSize is absent

2023-11-06 Thread Madhan Neethiraj


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




security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java
Line 615 (original)


searchProjects() method doesn't seem to exclude/filter any item retrieved 
from projectService.searchProjects(). It only does scrubbing of projects when 
requested permission is LIST.

Given this, is it necessary to retrieve entire projects list? Please review.



security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java
Line 261 (original), 261 (patched)


I suggest renaming DISABLE_PAGINATION to RETRIEVE_ALL_PAGES.

boolean skipPagination = isCountQuery || 
Boolean.parseBoolean(searchCriteria.getParam(SearchFilter.RETRIEVE_ALL_PAGES));

if (!skipPagination)) {
  query.setFirstResult(searchCriteria.getStartIndex());
  updateQueryPageSize(query, searchCriteria);
}



security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareService.java
Lines 294 (patched)


searchDataShares() is called from multiple places. Diabling of pagination 
may not be expected for all callers. I suggest to have the caller disable 
pagination where needed - like GdsDBStore.getUnscrubbedDataShares().

Please review and update other search() method as well for above:
 - RangerGdsDatasetService.searchDatasets()
 - RangerGdsProjectService.searchProject()
 - RangerGdsSharedResourceService.


- Madhan Neethiraj


On Nov. 3, 2023, 2:56 p.m., Prashant Satam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74681/
> ---
> 
> (Updated Nov. 3, 2023, 2:56 p.m.)
> 
> 
> Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, 
> Monika Kachhadiya, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4480
> https://issues.apache.org/jira/browse/RANGER-4480
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> In case of GDS existing pagination behaviour will not work as we have filters 
> after the DB results.Hence will not get appropriate paginated result
> 
> 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
> 2)If a user has 250 resources in DB trying to fetch single resource object 
> using query Param "resourceContains" which ranks 250th in position in DB he 
> will get empty response but the actual object is present in the DB, reason is 
> ranger has default pagination behaviour (i.e to fetch paginated objects in 
> batch size of 200) so DB result will have first 200 resource objects and then 
> filter of queryParam 'resourceContains' will be applied hence the output will 
> be empty as the expected object was never fetched from the DB beacuse of 
> pagination behavior 
> 3)So we need to disable this current pagination behaviour for GDS APIs 
> 
> So in case of GDS APIs we need to disable pagination
> 
> 
> Diffs
> -
> 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
> 93bd7f73d 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> 10986823d 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> 719d8a900 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDataShareService.java
>  6a93e44dc 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetService.java
>  072889f1d 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsProjectService.java
>  4ccb063fe 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsSharedResourceService.java
>  4bdb09f4d 
> 
> 
> Diff: https://reviews.apache.org/r/74681/diff/1/
> 
> 
> Testing
> ---
> 
> 1)Create shared resources more than default pageSize i.e 200
> 2)use GET-API > (/service/gds/resource) to fetch resource which has 
> resourceContains = resource_1 this shared resource should be beyond the 
> pageSize 200 
> 3)In response you will receive the shared resource having resource as 
> resource_1 which was beyond 200th position in DB
> Request -> (/service/gds/resource?resourceContains=resource_1)
> Response->
> {
> "startIndex": 0,
> "pageSize": 200,
> "totalCount": 1,
> "resultSize": 1,
> "sortType": "sharedResourceId",
> "sortBy": "asc",
> "queryTimeMS": 1697626402403,
> "list": [
> {
> "id": 388,
> "guid": "1d9e2fcf-8cc8-45b0-ab87-3f596c04350a",
>

Re: Review Request 74719: RANGER:4514:Sort params are interchanged in GDS API response

2023-11-06 Thread Madhan Neethiraj


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


Ship it!




Ship It!

- Madhan Neethiraj


On Nov. 6, 2023, 12:23 p.m., Prashant Satam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74719/
> ---
> 
> (Updated Nov. 6, 2023, 12:23 p.m.)
> 
> 
> Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, 
> Monika Kachhadiya, Subhrat Chaudhary, and Vanita Ubale.
> 
> 
> Bugs: RANGER-4514
> https://issues.apache.org/jira/browse/RANGER-4514
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> 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&sortType=ASC
> Expected: in response the sort params: sortBy=id, sortType=ASC
> Actual response:  sort params: sortBy=ASC, sortType=id
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> 4249b1121 
> 
> 
> Diff: https://reviews.apache.org/r/74719/diff/1/
> 
> 
> Testing
> ---
> 
> Testing Steps
> 1)Create 2 datasets
> 2)Fetch them using GET API - /service/gds/dataset?sortBy=id&sortType=ASC
> 3)In Response we get sortBy=ASC, sortType=id correctly
> Response
> {
> "startIndex": 0,
> "pageSize": 1,
> "totalCount": 3,
> "resultSize": 1,
> "sortType": "asc",
> "sortBy": "datasetId",
> "queryTimeMS": 1699273018014,
> "list": [
> {
> "id": 1,
> "guid": "51990db5-533e-4358-9fba-96758f93387f",
> "isEnabled": true,
> "createdBy": "Admin",
> "updatedBy": "Admin",
> "createTime": 1699010197633,
> "updateTime": 1699011093627,
> "version": 4,
> "description": "This is GDS description",
> "options": {
> "property1": "GDS_1_options",
> "property2": "GDS_2_options"
> },
> "additionalInfo": {
> "property1": "GDS_1_additionalInfo",
> "property2": "GDS_2_additionalInfo"
> },
> "name": "Test_GDS_Dataset1",
> "acl": {
> "users": {
> "admin": "ADMIN",
> "Test-User-1": "AUDIT"
> }
> },
> "termsOfUse": "Gds Terms of Use"
> }
> ],
> "listSize": 1
> }
> 
> 
> Thanks,
> 
> Prashant Satam
> 
>

[jira] [Commented] (RANGER-4491) Need new API for DataShare in Dataset Summary

2023-11-06 Thread Prashant Satam (Jira)



[ 
https://issues.apache.org/jira/browse/RANGER-4491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)

Re: Review Request 74701: RANGER-4493: Keep the UI behaviour for tag based and resource based services filtering for zone without any service

2023-11-06 Thread Brijesh Bhalala

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

(Updated Nov. 6, 2023, 12:56 p.m.)

Review request for ranger, Dhaval Rajpara and Mugdha Varadkar.

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

Repository: ranger

Description
---

In Ranger admin, security zones can be now created without any
services/resources.
If a security zone is created without any service, and on the service manager
page,
if the resource based services are filtered based on the zone without any
service,
then the UI displays an image with the text "No Services".
But if the same service filtering is done for tag based services, then the UI
shows a service element for tag.
It will be better if the UI behaviour is consistent for both resource and tag
based service filtering

In the current review request, I have improvise the code with following fixes :

1)Fix for the No service page in tag based.
2)Fix for the deleting the zone service while filtering zone.
3)Fix for import and export button click when there are no service while
filtering zone.

Diffs (updated)
-

security-admin/src/main/webapp/react-webapp/src/views/Home.jsx 3dee1d086

security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceDefinitions.jsx
0b2f46bec

security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceForm.jsx
2df0c4d63
security-admin/src/main/webapp/react-webapp/src/views/SideBar/TopNavBar.jsx
d4dbc57d1

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

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

Testing
---

Testing is in progress

Thanks,

Brijesh Bhalala

[jira] [Updated] (RANGER-4493) Keep the UI behaviour for tag based and resource based services filtering for zone without any service

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4493:

Attachment: 0002-RANGER-4493.patch

> Keep the UI behaviour for tag based and resource based services filtering for 
> zone without any service
> --
>
> Key: RANGER-4493
> URL: https://issues.apache.org/jira/browse/RANGER-4493
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Attachments: 0001-RANGER-4493.patch, 0002-RANGER-4493.patch, image 
> (10).png, image (9).png
>
>
> In Ranger admin, security zones can be now created without any 
> services/resources.
> If a security zone is created without any service, and on the service manager 
> page,
> if the resource based services are filtered based on the zone without any 
> service,
> then the UI displays an image with the text "No Services".
> But if the same service filtering is done for tag based services, then the UI 
> shows a service element for tag.
> It will be better if the UI behaviour is consistent for both resource and tag 
> based service filtering



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

[jira] [Updated] (RANGER-4493) Keep the UI behaviour for tag based and resource based services filtering for zone without any service

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4493:

Attachment: 0002-RANGER-4493.patch

> Keep the UI behaviour for tag based and resource based services filtering for 
> zone without any service
> --
>
> Key: RANGER-4493
> URL: https://issues.apache.org/jira/browse/RANGER-4493
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Attachments: 0001-RANGER-4493.patch, image (10).png, image (9).png
>
>
> In Ranger admin, security zones can be now created without any 
> services/resources.
> If a security zone is created without any service, and on the service manager 
> page,
> if the resource based services are filtered based on the zone without any 
> service,
> then the UI displays an image with the text "No Services".
> But if the same service filtering is done for tag based services, then the UI 
> shows a service element for tag.
> It will be better if the UI behaviour is consistent for both resource and tag 
> based service filtering



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

[jira] [Updated] (RANGER-4493) Keep the UI behaviour for tag based and resource based services filtering for zone without any service

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4493:

Attachment: (was: 0002-RANGER-4493.patch)

> Keep the UI behaviour for tag based and resource based services filtering for 
> zone without any service
> --
>
> Key: RANGER-4493
> URL: https://issues.apache.org/jira/browse/RANGER-4493
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Attachments: 0001-RANGER-4493.patch, image (10).png, image (9).png
>
>
> In Ranger admin, security zones can be now created without any 
> services/resources.
> If a security zone is created without any service, and on the service manager 
> page,
> if the resource based services are filtered based on the zone without any 
> service,
> then the UI displays an image with the text "No Services".
> But if the same service filtering is done for tag based services, then the UI 
> shows a service element for tag.
> It will be better if the UI behaviour is consistent for both resource and tag 
> based service filtering



--
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

2023-11-06 Thread Prashant Satam (Jira)



 [ 
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, version

[jira] [Updated] (RANGER-4448) GDS CRUD APIs should return proper response and message in case of failure

2023-11-06 Thread Prashant Satam (Jira)



 [ 
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

2023-11-06 Thread Prashant Satam (Jira)



 [ 
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

2023-11-06 Thread Prashant Satam (Jira)



 [ 
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

2023-11-06 Thread Prashant Satam (Jira)



 [ 
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&sortType=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)

Review Request 74719: RANGER:4514:Sort params are interchanged in GDS API response

2023-11-06 Thread Prashant Satam


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

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


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


Repository: ranger


Description
---

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&sortType=ASC
Expected: in response the sort params: sortBy=id, sortType=ASC
Actual response:  sort params: sortBy=ASC, sortType=id


Diffs
-

  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 4249b1121 


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


Testing
---

Testing Steps
1)Create 2 datasets
2)Fetch them using GET API - /service/gds/dataset?sortBy=id&sortType=ASC
3)In Response we get sortBy=ASC, sortType=id correctly
Response
{
"startIndex": 0,
"pageSize": 1,
"totalCount": 3,
"resultSize": 1,
"sortType": "asc",
"sortBy": "datasetId",
"queryTimeMS": 1699273018014,
"list": [
{
"id": 1,
"guid": "51990db5-533e-4358-9fba-96758f93387f",
"isEnabled": true,
"createdBy": "Admin",
"updatedBy": "Admin",
"createTime": 1699010197633,
"updateTime": 1699011093627,
"version": 4,
"description": "This is GDS description",
"options": {
"property1": "GDS_1_options",
"property2": "GDS_2_options"
},
"additionalInfo": {
"property1": "GDS_1_additionalInfo",
"property2": "GDS_2_additionalInfo"
},
"name": "Test_GDS_Dataset1",
"acl": {
"users": {
"admin": "ADMIN",
"Test-User-1": "AUDIT"
}
},
"termsOfUse": "Gds Terms of Use"
}
],
"listSize": 1
}


Thanks,

Prashant Satam

[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of error in request

2023-11-06 Thread Prashant Satam (Jira)



 [ 
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)

[jira] [Updated] (RANGER-4514) Sort params are interchanged in GDS API response

2023-11-06 Thread Prashant Satam (Jira)



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

Prashant Satam updated RANGER-4514:
---
Summary: Sort params are interchanged in GDS API response  (was: Sort 
params not working as expected for GDS APIs)

> 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
>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&sortType=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-4514) Sort params not working as expected for GDS APIs

2023-11-06 Thread Prashant Satam (Jira)



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

Prashant Satam updated RANGER-4514:
---
Description: 
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&sortType=ASC
 * Expected: in response the sort params: sortBy=id, sortType=ASC
 * Actual response:  sort params: sortBy=ASC, sortType=id

> Sort params not working as expected for GDS APIs
> 
>
> Key: RANGER-4514
> URL: https://issues.apache.org/jira/browse/RANGER-4514
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: 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&sortType=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] [Created] (RANGER-4514) Sort params not working as expected for GDS APIs

2023-11-06 Thread Prashant Satam (Jira)

Prashant Satam created RANGER-4514:
--

 Summary: Sort params not working as expected for GDS APIs
 Key: RANGER-4514
 URL: https://issues.apache.org/jira/browse/RANGER-4514
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Prashant Satam






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

[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of errors in request

2023-11-06 Thread Prashant Satam (Jira)



 [ 
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 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.

 

  was:
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 errors 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)

[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of errors in request

2023-11-06 Thread Prashant Satam (Jira)



 [ 
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 errors in 
request  (was: Handle exceptions in created sharedResource)

> Handle GDS APIs with appropriate response in case of errors 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
>
> 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)

[jira] [Updated] (RANGER-4513) Policy listing page experiences an unexpected reset to Access tab when attempting to filter the service and zone dropdown options.

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4513:

Summary: Policy listing page experiences an unexpected reset to Access tab 
when attempting to filter the service and zone dropdown options.   (was: Policy 
listing page experiences an unexpected reset to Access tabwhen attempting to 
filter the service and zone dropdown options. )

> Policy listing page experiences an unexpected reset to Access tab when 
> attempting to filter the service and zone dropdown options. 
> ---
>
> Key: RANGER-4513
> URL: https://issues.apache.org/jira/browse/RANGER-4513
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
>
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> *Steps to Reproduce:*
>  # Navigate to the "hive" policy listing page.
>  # Goto  Masking tab 
>  # Select the "Service" dropdown to filter policies based on a specific 
> service.
>  # Select the "Zone" dropdown to filter policies based on  specific zone.
>  # Observe that the page resets to the default "Access" tab
> *Expected Behavior:*
> The page should retain the selected tab when filtering the service and zone 
> dropdown.



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

[jira] [Updated] (RANGER-4513) Policy listing page experiences an unexpected reset to Access tabwhen attempting to filter the service and zone dropdown options.

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4513:

Summary: Policy listing page experiences an unexpected reset to Access 
tabwhen attempting to filter the service and zone dropdown options.   (was: 
Policy listing page experiences an unexpected reset when attempting to filter 
the service and zone dropdown options. )

> Policy listing page experiences an unexpected reset to Access tabwhen 
> attempting to filter the service and zone dropdown options. 
> --
>
> Key: RANGER-4513
> URL: https://issues.apache.org/jira/browse/RANGER-4513
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
>
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> *Steps to Reproduce:*
>  # Navigate to the "hive" policy listing page.
>  # Goto  Masking tab 
>  # Select the "Service" dropdown to filter policies based on a specific 
> service.
>  # Select the "Zone" dropdown to filter policies based on  specific zone.
>  # Observe that the page resets to the default "Access" tab
> *Expected Behavior:*
> The page should retain the selected tab when filtering the service and zone 
> dropdown.



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

[jira] [Updated] (RANGER-4513) Policy listing page experiences an unexpected reset when attempting to filter the service and zone dropdown options.

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4513:

Summary: Policy listing page experiences an unexpected reset when 
attempting to filter the service and zone dropdown options.   (was: Policy 
Listing Page Reset Issue when Filtering Service and Zone Dropdowns)

> Policy listing page experiences an unexpected reset when attempting to filter 
> the service and zone dropdown options. 
> -
>
> Key: RANGER-4513
> URL: https://issues.apache.org/jira/browse/RANGER-4513
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
>
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> *Steps to Reproduce:*
>  # Navigate to the "hive" policy listing page.
>  # Goto  Masking tab 
>  # Select the "Service" dropdown to filter policies based on a specific 
> service.
>  # Select the "Zone" dropdown to filter policies based on  specific zone.
>  # Observe that the page resets to the default "Access" tab
> *Expected Behavior:*
> The page should retain the selected tab when filtering the service and zone 
> dropdown.



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

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4513:

Description: 
The policy listing page experiences an unexpected reset when attempting to 
filter the service and zone dropdown options. 

*Steps to Reproduce:*
 # Navigate to the "hive" policy listing page.
 # Goto  Masking tab 
 # Select the "Service" dropdown to filter policies based on a specific service.
 # Select the "Zone" dropdown to filter policies based on  specific zone.
 # Observe that the page resets to the default "Access" tab

*Expected Behavior:*

The page should retain the selected tab when filtering the service and zone 
dropdown.{*}{{*}}

  was:
The policy listing page experiences an unexpected reset when attempting to 
filter the service and zone dropdown options. 

*Steps to Reproduce:*
 # Navigate to the "hive" policy listing page.
 # Goto  Masking tab 
 # Select the "Service" dropdown to filter policies based on a specific service.
 # Select the "Zone" dropdown to filter policies absed on  specific zone.
 # Observe that the page resets to the default "Access" tab

*Expected Behavior:*

The page should retain the selected tab when filtering the service and zone 
dropdown.{*}{*}


> Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns
> -
>
> Key: RANGER-4513
> URL: https://issues.apache.org/jira/browse/RANGER-4513
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
>
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> *Steps to Reproduce:*
>  # Navigate to the "hive" policy listing page.
>  # Goto  Masking tab 
>  # Select the "Service" dropdown to filter policies based on a specific 
> service.
>  # Select the "Zone" dropdown to filter policies based on  specific zone.
>  # Observe that the page resets to the default "Access" tab
> *Expected Behavior:*
> The page should retain the selected tab when filtering the service and zone 
> dropdown.{*}{{*}}



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

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4513:

Description: 
The policy listing page experiences an unexpected reset when attempting to 
filter the service and zone dropdown options. 

*Steps to Reproduce:*
 # Navigate to the "hive" policy listing page.
 # Goto  Masking tab 
 # Select the "Service" dropdown to filter policies based on a specific service.
 # Select the "Zone" dropdown to filter policies based on  specific zone.
 # Observe that the page resets to the default "Access" tab

*Expected Behavior:*

The page should retain the selected tab when filtering the service and zone 
dropdown.

  was:
The policy listing page experiences an unexpected reset when attempting to 
filter the service and zone dropdown options. 

*Steps to Reproduce:*
 # Navigate to the "hive" policy listing page.
 # Goto  Masking tab 
 # Select the "Service" dropdown to filter policies based on a specific service.
 # Select the "Zone" dropdown to filter policies based on  specific zone.
 # Observe that the page resets to the default "Access" tab

*Expected Behavior:*

The page should retain the selected tab when filtering the service and zone 
dropdown.{*}{{*}}


> Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns
> -
>
> Key: RANGER-4513
> URL: https://issues.apache.org/jira/browse/RANGER-4513
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
>
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> *Steps to Reproduce:*
>  # Navigate to the "hive" policy listing page.
>  # Goto  Masking tab 
>  # Select the "Service" dropdown to filter policies based on a specific 
> service.
>  # Select the "Zone" dropdown to filter policies based on  specific zone.
>  # Observe that the page resets to the default "Access" tab
> *Expected Behavior:*
> The page should retain the selected tab when filtering the service and zone 
> dropdown.



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

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4513:

Issue Type: Improvement  (was: Bug)

> Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns
> -
>
> Key: RANGER-4513
> URL: https://issues.apache.org/jira/browse/RANGER-4513
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> *Steps to Reproduce:*
>  # Navigate to the "hive" policy listing page.
>  # Goto  Masking tab 
>  # Select the "Service" dropdown to filter policies based on a specific 
> service.
>  # Select the "Zone" dropdown to filter policies absed on  specific zone.
>  # Observe that the page resets to the default "Access" tab
> *Expected Behavior:*
> The page should retain the selected tab when filtering the service and zone 
> dropdown.{*}{*}



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

[jira] [Created] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

2023-11-06 Thread Brijesh Bhalala (Jira)

Brijesh Bhalala created RANGER-4513:
---

 Summary: Policy Listing Page Reset Issue when Filtering Service 
and Zone Dropdowns
 Key: RANGER-4513
 URL: https://issues.apache.org/jira/browse/RANGER-4513
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Brijesh Bhalala
Assignee: Brijesh Bhalala


The policy listing page experiences an unexpected reset when attempting to 
filter the service and zone dropdown options. 

*Steps to Reproduce:*
 # Navigate to the "hive" policy listing page.
 # Goto  Masking tab 
 # Select the "Service" dropdown to filter policies based on a specific service.
 # Select the "Zone" dropdown to filter policies absed on  specific zone.
 # Observe that the page resets to the default "Access" tab

*Expected Behavior:*

The page should retain the selected tab when filtering the service and zone 
dropdown.{*}{*}



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

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4513:

Labels: ranger-react  (was: )

> Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns
> -
>
> Key: RANGER-4513
> URL: https://issues.apache.org/jira/browse/RANGER-4513
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
>
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> *Steps to Reproduce:*
>  # Navigate to the "hive" policy listing page.
>  # Goto  Masking tab 
>  # Select the "Service" dropdown to filter policies based on a specific 
> service.
>  # Select the "Zone" dropdown to filter policies absed on  specific zone.
>  # Observe that the page resets to the default "Access" tab
> *Expected Behavior:*
> The page should retain the selected tab when filtering the service and zone 
> dropdown.{*}{*}



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

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

2023-11-06 Thread Brijesh Bhalala (Jira)



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

Brijesh Bhalala updated RANGER-4513:

Fix Version/s: 3.0.0

> Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns
> -
>
> Key: RANGER-4513
> URL: https://issues.apache.org/jira/browse/RANGER-4513
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
> Fix For: 3.0.0
>
>
> The policy listing page experiences an unexpected reset when attempting to 
> filter the service and zone dropdown options. 
> *Steps to Reproduce:*
>  # Navigate to the "hive" policy listing page.
>  # Goto  Masking tab 
>  # Select the "Service" dropdown to filter policies based on a specific 
> service.
>  # Select the "Zone" dropdown to filter policies absed on  specific zone.
>  # Observe that the page resets to the default "Access" tab
> *Expected Behavior:*
> The page should retain the selected tab when filtering the service and zone 
> dropdown.{*}{*}



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

Re: Review Request 74720: RANGER-4283: [WIP] UI for GDS: UI Design changes for add principal, internal tab listing and CSS changes

Re: Review Request 74720: RANGER-4283: [WIP] UI for GDS: UI Design changes for add principal, internal tab listing and CSS changes

Review Request 74720: RANGER-4283: [WIP] UI for GDS: UI Design changes for add principal, internal tab listing and CSS changes

[jira] (RANGER-4480) Pagination with default pageSize gets applied, even when pagination param pageSize is absent

org.apache.ranger.authorization.hive.authorizer.RangerHiveAuthorizerFactory ClassNotFoundException

Re: Review Request 74717: RANGER-4378: removed static PolicyEngine.impliedAccessGrants

Re: Apply for contributor permissions

Re: Review Request 74681: RANGER:4480:Pagination with default pageSize gets applied, even when pagination param pageSize is absent

Re: Review Request 74719: RANGER:4514:Sort params are interchanged in GDS API response

[jira] [Commented] (RANGER-4491) Need new API for DataShare in Dataset Summary

Re: Review Request 74701: RANGER-4493: Keep the UI behaviour for tag based and resource based services filtering for zone without any service

[jira] [Updated] (RANGER-4493) Keep the UI behaviour for tag based and resource based services filtering for zone without any service

[jira] [Updated] (RANGER-4493) Keep the UI behaviour for tag based and resource based services filtering for zone without any service

[jira] [Updated] (RANGER-4493) Keep the UI behaviour for tag based and resource based services filtering for zone without any service

[jira] [Updated] (RANGER-4448) GDS CRUD APIs should return proper response and message in case of failure

[jira] [Updated] (RANGER-4448) GDS CRUD APIs should return proper response and message in case of failure

[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of error in request

[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of error in request

[jira] [Assigned] (RANGER-4514) Sort params are interchanged in GDS API response

Review Request 74719: RANGER:4514:Sort params are interchanged in GDS API response

[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of error in request

[jira] [Updated] (RANGER-4514) Sort params are interchanged in GDS API response

[jira] [Updated] (RANGER-4514) Sort params not working as expected for GDS APIs

[jira] [Created] (RANGER-4514) Sort params not working as expected for GDS APIs

[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of errors in request

[jira] [Updated] (RANGER-4448) Handle GDS APIs with appropriate response in case of errors in request

[jira] [Updated] (RANGER-4513) Policy listing page experiences an unexpected reset to Access tab when attempting to filter the service and zone dropdown options.

[jira] [Updated] (RANGER-4513) Policy listing page experiences an unexpected reset to Access tabwhen attempting to filter the service and zone dropdown options.

[jira] [Updated] (RANGER-4513) Policy listing page experiences an unexpected reset when attempting to filter the service and zone dropdown options.

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

[jira] [Created] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

[jira] [Updated] (RANGER-4513) Policy Listing Page Reset Issue when Filtering Service and Zone Dropdowns

35 matches

Site Navigation

Mail list logo

Footer information