[jira] [Assigned] (RANGER-4710) HS2 logs having huge number of WARN logs from RangerHiveAuthorizer regarding connection to HMS for fetching hive object owner

[Dineshkumar Yadav (Jira)]

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

Dineshkumar Yadav reassigned RANGER-4710:
-

Assignee: Dineshkumar Yadav

> HS2 logs having huge number of WARN logs from RangerHiveAuthorizer regarding 
> connection to HMS for fetching hive object owner
> -
>
> Key: RANGER-4710
> URL: https://issues.apache.org/jira/browse/RANGER-4710
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Reporter: suja s
>Assignee: Dineshkumar Yadav
>Priority: Major
>
> CURRENT BEHAVIOUR:
> HS2 logs having huge number of WARN logs from RangerHiveAuthorizer indicating 
> connection to HMS for fetching hive object owner
> EXPECTED BEHAVIOUR:
> Reduce the log level to DEBUG if this is expected behaviour.



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

[jira] [Updated] (RANGER-4719) Policy condition expressions are split by the Ranger UI on commas

[Himanshu Maurya (Jira)]

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

Himanshu Maurya updated RANGER-4719:

Fix Version/s: 3.0.0
   2.4.0

>  Policy condition expressions are split by the Ranger UI on commas
> --
>
> Key: RANGER-4719
> URL: https://issues.apache.org/jira/browse/RANGER-4719
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot 
> 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png, 
> Screenshot 2024-02-20 at 5.26.46 PM.png, image-2024-02-20-17-28-17-767.png, 
> image-2024-02-20-17-28-28-558.png, image-2024-02-20-17-39-05-432.png
>
>
> While using attributes with default values introduced in 
> [RANGER-3997|https://issues.apache.org/jira/browse/RANGER-3997] like 
> GET_USER_ATTR('state', 'null') in policy condition.
> It is observed that ranger is splitting condition string in to 2 parts 
> separated by comma of the parameters passed to GET_USER_ATTR(), due to this 
> it is not taking default value and conditions are converted to invalid 
> strings.
> Kindly refer to screenshots attached below.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>  
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>  
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!



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

Re: Review Request 74900: RANGER-4722: HDFS authorization logic for directory hierarchy rooted at "/" is incorrect

[Sailaja Polavarapu]

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


Ship it!




Ship It!

- Sailaja Polavarapu


On Feb. 20, 2024, 11:35 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74900/
> ---
> 
> (Updated Feb. 20, 2024, 11:35 p.m.)
> 
> 
> Review request for ranger, madhan, Madhan Neethiraj, Ramesh Mani, and Sailaja 
> Polavarapu.
> 
> 
> Bugs: RANGER-4722
> https://issues.apache.org/jira/browse/RANGER-4722
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger authorization logic for the HDFS commands that require authorization 
> of the entire directory hierarchy rooted at the specified directory argument 
> is incorrect as it does not correctly compute the sub-directory paths. The 
> paths of sub-directories that need to be authorized incorrectly contain an 
> extra '/' character, which leads to incorrect authorization result.
> 
> 
> Diffs
> -
> 
>   
> hdfs-agent/src/main/java/org/apache/ranger/authorization/hadoop/RangerHdfsAuthorizer.java
>  9b1279bcb 
> 
> 
> Diff: https://reviews.apache.org/r/74900/diff/1/
> 
> 
> Testing
> ---
> 
> Compiles clean and passes unit tests.
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: Review Request 74899: RANGER-4630: Added support for multiple tag resource id search in resources/paginated api, and by tagServiceName in tagresourcemaps/paginated api

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On Feb. 21, 2024, 3:21 a.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74899/
> ---
> 
> (Updated Feb. 21, 2024, 3:21 a.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4630
> https://issues.apache.org/jira/browse/RANGER-4630
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Added support for multiple tag resource id search in resources/paginated api, 
> and by tagServiceName in tagresourcemaps/paginated api
> 
> 
> Diffs
> -
> 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
> d1568bbac 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> 529472a31 
>   security-admin/src/main/java/org/apache/ranger/rest/TagREST.java 01ff442fb 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerServiceResourceService.java
>  989ea2259 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerTagResourceMapService.java
>  f22963f3c 
> 
> 
> Diff: https://reviews.apache.org/r/74899/diff/2/
> 
> 
> Testing
> ---
> 
> Validated multiple tag resource id search in tags/resources/paginated api
> Validated search by tagServiceName in tagresourcemaps/paginated api
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>

Re: Review Request 74899: RANGER-4630: Added support for multiple tag resource id search in resources/paginated api, and by tagServiceName in tagresourcemaps/paginated api

[Anand Nadar]

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

(Updated Feb. 21, 2024, 3:21 a.m.)


Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika Kachhadiya, 
Siddhesh Phatak, and Subhrat Chaudhary.


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


Repository: ranger


Description
---

Added support for multiple tag resource id search in resources/paginated api, 
and by tagServiceName in tagresourcemaps/paginated api


Diffs (updated)
-

  agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
d1568bbac 
  security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
529472a31 
  security-admin/src/main/java/org/apache/ranger/rest/TagREST.java 01ff442fb 
  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceResourceService.java
 989ea2259 
  
security-admin/src/main/java/org/apache/ranger/service/RangerTagResourceMapService.java
 f22963f3c 


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

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


Testing
---

Validated multiple tag resource id search in tags/resources/paginated api
Validated search by tagServiceName in tagresourcemaps/paginated api


Thanks,

Anand Nadar

Re: Review Request 74900: RANGER-4722: HDFS authorization logic for directory hierarchy rooted at "/" is incorrect

[Abhay Kulkarni]

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

(Updated Feb. 20, 2024, 11:23 p.m.)


Review request for ranger, madhan, Madhan Neethiraj, and Ramesh Mani.


Changes
---

Updated Ranger JIRA and description


Summary (updated)
-

RANGER-4722: HDFS authorization logic for directory hierarchy rooted at "/" is 
incorrect


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


Repository: ranger


Description (updated)
---

Ranger authorization logic for the HDFS commands that require authorization of 
the entire directory hierarchy rooted at the specified directory argument is 
incorrect as it does not correctly compute the sub-directory paths. The paths 
of sub-directories that need to be authorized incorrectly contain an extra '/' 
character, which leads to incorrect authorization result.


Diffs
-

  
hdfs-agent/src/main/java/org/apache/ranger/authorization/hadoop/RangerHdfsAuthorizer.java
 9b1279bcb 


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


Testing (updated)
---

Compiles clean and passes unit tests.


Thanks,

Abhay Kulkarni

[jira] [Created] (RANGER-4722) HDFS authorization logic for directory hierarchy rooted at "/" is incorrect

[Abhay Kulkarni (Jira)]

Abhay Kulkarni created RANGER-4722:
--

 Summary: HDFS authorization logic for directory hierarchy rooted 
at "/" is incorrect
 Key: RANGER-4722
 URL: https://issues.apache.org/jira/browse/RANGER-4722
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Abhay Kulkarni
Assignee: Abhay Kulkarni


Ranger authorization logic for the HDFS commands that require authorization of 
the entire directory hierarchy rooted at the specified directory argument is 
incorrect as it does not correctly compute the sub-directory paths. The paths 
of sub-directories that need to be authorized incorrectly contain an extra '/' 
character, which leads to incorrect authorization result.



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

Re: Review Request 74897: RANGER-4719: Policy condition expressions are split by the Ranger UI on commas

[Madhan Neethiraj]

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




security-admin/src/main/webapp/scripts/views/policies/RangerPolicyForm.js
Lines 522 (patched)


Instead of looking for PolicyCondition.type == "_expression", consider 
checking for one of the following in RangerPolicyConditionDef:
 - evaluator == 
"org.apache.ranger.plugin.conditionevaluator.RangerScriptConditionEvaluator"
 - evaluatorOptions["ui.isMultiline"] == "true"


- Madhan Neethiraj


On Feb. 20, 2024, 11:52 a.m., Himanshu Maurya wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74897/
> ---
> 
> (Updated Feb. 20, 2024, 11:52 a.m.)
> 
> 
> Review request for ranger, bhavik patel, Dhaval Shah, Dineshkumar Yadav, 
> Harshal Chavan, Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Nitin 
> Galave, Pradeep Agrawal, and Velmurugan Periasamy.
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> While using attributes with default values introduced in RANGER-3997 like 
> GET_USER_ATTR('state', 'null') in policy condition.
> It is observed that ranger is splitting condition string in to parts 
> separated by comma of the parameters passed to GET_USER_ATTR(), due to this 
> it is not taking default value and conditions are converted to invalid 
> strings.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/scripts/views/policies/RangerPolicyForm.js 
> 5f6d9ac01 
> 
> 
> Diff: https://reviews.apache.org/r/74897/diff/1/
> 
> 
> Testing
> ---
> 
> Done the required code changes and installed ranger.
> Validated the policy conditions with default comma separated parameters 
> passed with attributes.
> 
> 
> Thanks,
> 
> Himanshu Maurya
> 
>

Re: Review Request 74899: RANGER-4630: Added support for multiple tag resource id search in resources/paginated api, and by tagServiceName in tagresourcemaps/paginated api

[Madhan Neethiraj]

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




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


svce => svcr


- Madhan Neethiraj


On Feb. 20, 2024, 7:44 p.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74899/
> ---
> 
> (Updated Feb. 20, 2024, 7:44 p.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4630
> https://issues.apache.org/jira/browse/RANGER-4630
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Added support for multiple tag resource id search in resources/paginated api, 
> and by tagServiceName in tagresourcemaps/paginated api
> 
> 
> Diffs
> -
> 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
> d1568bbac 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> 529472a31 
>   security-admin/src/main/java/org/apache/ranger/rest/TagREST.java 01ff442fb 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerServiceResourceService.java
>  989ea2259 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerTagResourceMapService.java
>  f22963f3c 
> 
> 
> Diff: https://reviews.apache.org/r/74899/diff/1/
> 
> 
> Testing
> ---
> 
> Validated multiple tag resource id search in tags/resources/paginated api
> Validated search by tagServiceName in tagresourcemaps/paginated api
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>

Review Request 74899: RANGER-4630: Added support for multiple tag resource id search in resources/paginated api, and by tagServiceName in tagresourcemaps/paginated api

[Anand Nadar]

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

Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika Kachhadiya, 
Siddhesh Phatak, and Subhrat Chaudhary.


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


Repository: ranger


Description
---

Added support for multiple tag resource id search in resources/paginated api, 
and by tagServiceName in tagresourcemaps/paginated api


Diffs
-

  agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
d1568bbac 
  security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
529472a31 
  security-admin/src/main/java/org/apache/ranger/rest/TagREST.java 01ff442fb 
  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceResourceService.java
 989ea2259 
  
security-admin/src/main/java/org/apache/ranger/service/RangerTagResourceMapService.java
 f22963f3c 


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


Testing
---

Validated multiple tag resource id search in tags/resources/paginated api
Validated search by tagServiceName in tagresourcemaps/paginated api


Thanks,

Anand Nadar

Review Request 74898: RANGER-4680 : Inconsistent resource lookup behaviour with newly created service.

[Dhaval Rajpara]

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

Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Kishor 
Gollapalliwar, Madhan Neethiraj, Mehul Parikh, and Mugdha Varadkar.


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


Repository: ranger


Description
---

For newly created service, on policy create page, entering text in the resource 
field doesn't trigger the corresponding resource lookup API.

Upon reloading the page the resource lookup api is getting called.

 

Steps to repro:

1) Create a new Hive service.

2) Go to policy listing page of above created service

3) Click on Add New Policy button for creating new policy.

4) In Hive Database resource field enter some text.


Diffs
-

  
security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AccessLogDetail.jsx
 13b775810 
  
security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AccessLogs.jsx 
8e12ec654 
  
security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyViewDetails.jsx
 b8e4650f7 
  
security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/PluginStatusLogs.jsx
 d798a5fd5 
  
security-admin/src/main/webapp/react-webapp/src/views/Encryption/KeyCreate.jsx 
aa1788772 
  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/AddUpdatePolicyForm.jsx
 9cf87b276 
  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyListingTabView.jsx
 6fffb60a9 
  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
 706c51578 
  
security-admin/src/main/webapp/react-webapp/src/views/Reports/UserAccessLayout.jsx
 fda70d9bb 
  
security-admin/src/main/webapp/react-webapp/src/views/SecurityZone/SecurityZoneForm.jsx
 cddf0606d 
  
security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceDefinitions.jsx
 49d93ee4a 
  
security-admin/src/main/webapp/react-webapp/src/views/ServiceManager/ServiceForm.jsx
 99808da34 
  security-admin/src/main/webapp/react-webapp/src/views/SideBar/SideBar.jsx 
346440acc 


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


Testing
---

Testing is in progress


Thanks,

Dhaval Rajpara

[jira] [Updated] (RANGER-4680) Inconsistent resource lookup behaviour with newly created service

[Dhaval Rajpara (Jira)]

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

Dhaval Rajpara updated RANGER-4680:
---
Attachment: 0001-RANGER-4680.patch

> Inconsistent resource lookup behaviour with newly created service
> -
>
> Key: RANGER-4680
> URL: https://issues.apache.org/jira/browse/RANGER-4680
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Vishal Bhavsar
>Assignee: Dhaval Rajpara
>Priority: Major
> Attachments: 0001-RANGER-4680.patch
>
>
> For newly created service, on policy create page, entering text in the 
> resource field doesn't trigger the corresponding resource lookup API.
> Upon reloading the page the resource lookup api is getting called.
>  
> Steps to repro:
> 1) Create a new Hive service.
> 2) Go to policy listing page of above created service
> 3) Click on Add New Policy button for creating new policy.
> 4) In Hive Database resource field enter some text. 



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

[jira] [Updated] (RANGER-4719) Policy condition expressions are split by the Ranger UI on commas

[Himanshu Maurya (Jira)]

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

Himanshu Maurya updated RANGER-4719:

Attachment: image-2024-02-20-17-39-05-432.png

>  Policy condition expressions are split by the Ranger UI on commas
> --
>
> Key: RANGER-4719
> URL: https://issues.apache.org/jira/browse/RANGER-4719
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot 
> 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png, 
> Screenshot 2024-02-20 at 5.26.46 PM.png, image-2024-02-20-17-28-17-767.png, 
> image-2024-02-20-17-28-28-558.png, image-2024-02-20-17-39-05-432.png
>
>
> While using attributes with default values introduced in 
> [RANGER-3997|https://issues.apache.org/jira/browse/RANGER-3997] like 
> GET_USER_ATTR('state', 'null') in policy condition.
> It is observed that ranger is splitting condition string in to 2 parts 
> separated by comma of the parameters passed to GET_USER_ATTR(), due to this 
> it is not taking default value and conditions are converted to invalid 
> strings.
> Kindly refer to screenshots attached below.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>  
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>  
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!



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

[jira] [Commented] (RANGER-4719) Policy condition expressions are split by the Ranger UI on commas

[Himanshu Maurya (Jira)]

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

Himanshu Maurya commented on RANGER-4719:
-

Hi [~madhan] 

I have debugged this issue, fixed and validated

!Screenshot 2024-02-20 at 5.26.46 PM.png|width=702,height=424!

!image-2024-02-20-17-28-28-558.png|width=709,height=139!

!image-2024-02-20-17-39-05-432.png|width=707,height=146!

Kindly review and merge 
Review board link :- [https://reviews.apache.org/r/74897/]

Thanks and Regards

>  Policy condition expressions are split by the Ranger UI on commas
> --
>
> Key: RANGER-4719
> URL: https://issues.apache.org/jira/browse/RANGER-4719
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot 
> 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png, 
> Screenshot 2024-02-20 at 5.26.46 PM.png, image-2024-02-20-17-28-17-767.png, 
> image-2024-02-20-17-28-28-558.png, image-2024-02-20-17-39-05-432.png
>
>
> While using attributes with default values introduced in 
> [RANGER-3997|https://issues.apache.org/jira/browse/RANGER-3997] like 
> GET_USER_ATTR('state', 'null') in policy condition.
> It is observed that ranger is splitting condition string in to 2 parts 
> separated by comma of the parameters passed to GET_USER_ATTR(), due to this 
> it is not taking default value and conditions are converted to invalid 
> strings.
> Kindly refer to screenshots attached below.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>  
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>  
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!



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

[jira] [Updated] (RANGER-4719) Policy condition expressions are split by the Ranger UI on commas

[Himanshu Maurya (Jira)]

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

Himanshu Maurya updated RANGER-4719:

Attachment: image-2024-02-20-17-28-17-767.png

>  Policy condition expressions are split by the Ranger UI on commas
> --
>
> Key: RANGER-4719
> URL: https://issues.apache.org/jira/browse/RANGER-4719
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot 
> 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png, 
> Screenshot 2024-02-20 at 5.26.46 PM.png, image-2024-02-20-17-28-17-767.png, 
> image-2024-02-20-17-28-28-558.png
>
>
> While using attributes with default values introduced in 
> [RANGER-3997|https://issues.apache.org/jira/browse/RANGER-3997] like 
> GET_USER_ATTR('state', 'null') in policy condition.
> It is observed that ranger is splitting condition string in to 2 parts 
> separated by comma of the parameters passed to GET_USER_ATTR(), due to this 
> it is not taking default value and conditions are converted to invalid 
> strings.
> Kindly refer to screenshots attached below.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>  
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>  
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!



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

[jira] [Updated] (RANGER-4719) Policy condition expressions are split by the Ranger UI on commas

[Himanshu Maurya (Jira)]

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

Himanshu Maurya updated RANGER-4719:

Attachment: image-2024-02-20-17-28-28-558.png

>  Policy condition expressions are split by the Ranger UI on commas
> --
>
> Key: RANGER-4719
> URL: https://issues.apache.org/jira/browse/RANGER-4719
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot 
> 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png, 
> Screenshot 2024-02-20 at 5.26.46 PM.png, image-2024-02-20-17-28-17-767.png, 
> image-2024-02-20-17-28-28-558.png
>
>
> While using attributes with default values introduced in 
> [RANGER-3997|https://issues.apache.org/jira/browse/RANGER-3997] like 
> GET_USER_ATTR('state', 'null') in policy condition.
> It is observed that ranger is splitting condition string in to 2 parts 
> separated by comma of the parameters passed to GET_USER_ATTR(), due to this 
> it is not taking default value and conditions are converted to invalid 
> strings.
> Kindly refer to screenshots attached below.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>  
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>  
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!



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

[jira] [Updated] (RANGER-4719) Policy condition expressions are split by the Ranger UI on commas

[Himanshu Maurya (Jira)]

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

Himanshu Maurya updated RANGER-4719:

Attachment: Screenshot 2024-02-20 at 5.26.46 PM.png

>  Policy condition expressions are split by the Ranger UI on commas
> --
>
> Key: RANGER-4719
> URL: https://issues.apache.org/jira/browse/RANGER-4719
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot 
> 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png, 
> Screenshot 2024-02-20 at 5.26.46 PM.png
>
>
> While using attributes with default values introduced in 
> [RANGER-3997|https://issues.apache.org/jira/browse/RANGER-3997] like 
> GET_USER_ATTR('state', 'null') in policy condition.
> It is observed that ranger is splitting condition string in to 2 parts 
> separated by comma of the parameters passed to GET_USER_ATTR(), due to this 
> it is not taking default value and conditions are converted to invalid 
> strings.
> Kindly refer to screenshots attached below.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>  
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>  
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!



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

Review Request 74897: RANGER-4719: Policy condition expressions are split by the Ranger UI on commas

[Himanshu Maurya]

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

Review request for ranger, bhavik patel, Dhaval Shah, Dineshkumar Yadav, 
Harshal Chavan, Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Nitin 
Galave, Pradeep Agrawal, and Velmurugan Periasamy.


Repository: ranger


Description
---

While using attributes with default values introduced in RANGER-3997 like 
GET_USER_ATTR('state', 'null') in policy condition.
It is observed that ranger is splitting condition string in to parts separated 
by comma of the parameters passed to GET_USER_ATTR(), due to this it is not 
taking default value and conditions are converted to invalid strings.


Diffs
-

  security-admin/src/main/webapp/scripts/views/policies/RangerPolicyForm.js 
5f6d9ac01 


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


Testing
---

Done the required code changes and installed ranger.
Validated the policy conditions with default comma separated parameters passed 
with attributes.


Thanks,

Himanshu Maurya

[jira] [Updated] (RANGER-4719) Policy condition expressions are split by the Ranger UI on commas

[Himanshu Maurya (Jira)]

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

Himanshu Maurya updated RANGER-4719:

Description: 
While using attributes with default values introduced in 
[RANGER-3997|https://issues.apache.org/jira/browse/RANGER-3997] like 
GET_USER_ATTR('state', 'null') in policy condition.
It is observed that ranger is splitting condition string in to 2 parts 
separated by comma of the parameters passed to GET_USER_ATTR(), due to this it 
is not taking default value and conditions are converted to invalid strings.
Kindly refer to screenshots attached below.

!Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!

 

!Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!

 

!Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!

  was:
While using GET_USER_ATTR('state', 'null') in policy condition.
It is observed that ranger is splitting condition string in to 2 parts 
separated by comma of the parameters passed to GET_USER_ATTR(), due to this it 
is not taking default value and conditions are converted to invalid strings.
Kindly refer to screenshots attached below.

!Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!

 

!Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!

 

!Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!


>  Policy condition expressions are split by the Ranger UI on commas
> --
>
> Key: RANGER-4719
> URL: https://issues.apache.org/jira/browse/RANGER-4719
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot 
> 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png
>
>
> While using attributes with default values introduced in 
> [RANGER-3997|https://issues.apache.org/jira/browse/RANGER-3997] like 
> GET_USER_ATTR('state', 'null') in policy condition.
> It is observed that ranger is splitting condition string in to 2 parts 
> separated by comma of the parameters passed to GET_USER_ATTR(), due to this 
> it is not taking default value and conditions are converted to invalid 
> strings.
> Kindly refer to screenshots attached below.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>  
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>  
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!



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

[jira] [Updated] (RANGER-4630) Need to add pagination support and searchFilters for tag related APIs

[Anand Nadar (Jira)]

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

Anand Nadar updated RANGER-4630:

Description: 
Currently for Tag related GET-APIs i.e for 
(RangerTags,RangerTagDefs,RangerServiceResource) we dont support pagination,and 
also we need additional searchFilters for them

 

1) Tags
    Request > /service/tags/tags/paginated?
Supported Query Params 
    Search Fields
        tagId,tagDefId,tagType,tagTypePartial
        multiple tagId search
    Sort Fields
        tagId,tagDefId,createTime,updateTime
    Supports Pagination

2) TagDefs
    Request > /service/tags/tagdefs/paginated?
Supported Query Params 
    Search Fields
tagDefId,tagDefGuid,tagType,tagTypePartial,tagSource,
tagSourcePartial
    Sort Fields
        tagDefId,tagType,createTime,updateTime
    Supports Pagination

3) ServiceResource
    Request > /service/tags/resources/paginated?
Supported Query Params 
    Search Fields
resourceId,tagServiceId,tagServiceName,tagServiceNamePartial,resourceGuid,resourceSignature
multiple resourceId search
    Sort Fields
        resourceId,tagServiceId,createTime,updateTime
    Supports Pagination

4) TagResourceMaps
Request => service/tags/tagresourcemaps/paginated
Search fields - tagId, resourceId, serviceName
Sort Fields - tagId, resourceId, tagDefId
Supports pagination

  was:
Currently for Tag related GET-APIs i.e for 
(RangerTags,RangerTagDefs,RangerServiceResource) we dont support pagination,and 
also we need additional searchFilters for them

 

1) Tags
    Request > /service/tags/tags/paginated?
Supported Query Params 
    Search Fields
        tagId,tagDefId,tagType,tagTypePartial
        multiple tagId search
    Sort Fields
        tagId,tagDefId,createTime,updateTime
    Supports Pagination

2) TagDefs
    Request > /service/tags/tagdefs/paginated?
Supported Query Params 
    Search Fields
tagDefId,tagDefGuid,tagType,tagTypePartial,tagSource,
tagSourcePartial
    Sort Fields
        tagDefId,tagType,createTime,updateTime
    Supports Pagination

3) ServiceResource
    Request > /service/tags/resources/paginated?
Supported Query Params 
    Search Fields
resourceId,tagServiceId,tagServiceName,tagServiceNamePartial,resourceGuid,resourceSignature
multiple resourceId search
    Sort Fields
        resourceId,tagServiceId,createTime,updateTime
    Supports Pagination

4) TagResourceMaps
Request => service/tags/tagresourcemaps/paginated
Search fields - tagId, resourceId, serviceName
Supports pagination


> Need to add pagination support and searchFilters for tag related APIs
> -
>
> Key: RANGER-4630
> URL: https://issues.apache.org/jira/browse/RANGER-4630
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Anand Nadar
>Priority: Minor
> Fix For: 3.0.0
>
>
> Currently for Tag related GET-APIs i.e for 
> (RangerTags,RangerTagDefs,RangerServiceResource) we dont support 
> pagination,and also we need additional searchFilters for them
>  
> 1) Tags
>     Request > /service/tags/tags/paginated?
> Supported Query Params 
>     Search Fields
>         tagId,tagDefId,tagType,tagTypePartial
>         multiple tagId search
>     Sort Fields
>         tagId,tagDefId,createTime,updateTime
>     Supports Pagination
> 2) TagDefs
>     Request > /service/tags/tagdefs/paginated?
> Supported Query Params 
>     Search Fields
> tagDefId,tagDefGuid,tagType,tagTypePartial,tagSource,
> tagSourcePartial
>     Sort Fields
>         tagDefId,tagType,createTime,updateTime
>     Supports Pagination
> 3) ServiceResource
>     Request > /service/tags/resources/paginated?
> Supported Query Params 
>     Search Fields
> resourceId,tagServiceId,tagServiceName,tagServiceNamePartial,resourceGuid,resourceSignature
> multiple resourceId search
>     Sort Fields
>         resourceId,tagServiceId,createTime,updateTime
>     Supports Pagination
> 4) TagResourceMaps
> Request => service/tags/tagresourcemaps/paginated
> Search fields - tagId, resourceId, serviceName
> Sort Fields - tagId, resourceId, tagDefId
> Supports pagination



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

[jira] [Updated] (RANGER-4630) Need to add pagination support and searchFilters for tag related APIs

[Anand Nadar (Jira)]

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

Anand Nadar updated RANGER-4630:

Description: 
Currently for Tag related GET-APIs i.e for 
(RangerTags,RangerTagDefs,RangerServiceResource) we dont support pagination,and 
also we need additional searchFilters for them

 

1) Tags
    Request > /service/tags/tags/paginated?
Supported Query Params 
    Search Fields
        tagId,tagDefId,tagType,tagTypePartial
        multiple tagId search
    Sort Fields
        tagId,tagDefId,createTime,updateTime
    Supports Pagination

2) TagDefs
    Request > /service/tags/tagdefs/paginated?
Supported Query Params 
    Search Fields
tagDefId,tagDefGuid,tagType,tagTypePartial,tagSource,
tagSourcePartial
    Sort Fields
        tagDefId,tagType,createTime,updateTime
    Supports Pagination

3) ServiceResource
    Request > /service/tags/resources/paginated?
Supported Query Params 
    Search Fields
resourceId,tagServiceId,tagServiceName,tagServiceNamePartial,resourceGuid,resourceSignature
multiple resourceId search
    Sort Fields
        resourceId,tagServiceId,createTime,updateTime
    Supports Pagination

4) TagResourceMaps
Request => service/tags/tagresourcemaps/paginated
Search fields - tagId, resourceId, serviceName
Supports pagination

  was:
Currently for Tag related GET-APIs i.e for 
(RangerTags,RangerTagDefs,RangerServiceResource) we dont support pagination,and 
also we need additional searchFilters for them

 

1) Tags
    Request > /service/tags/tags/paginated?
Supported Query Params 
    Search Fields
        tagId,tagDefId,tagType,tagTypePartial
        multiple tagId search
    Sort Fields
        tagId,tagDefId,createTime,updateTime
    Supports Pagination


2) TagDefs
    Request > /service/tags/tagdefs/paginated?
Supported Query Params 
    Search Fields
tagDefId,tagDefGuid,tagType,tagTypePartial,tagSource,
tagSourcePartial
    Sort Fields
        tagDefId,tagType,createTime,updateTime
    Supports Pagination


3) ServiceResource
    Request > /service/tags/resources/paginated?
Supported Query Params 
    Search Fields
resourceId,tagServiceId,tagServiceName,tagServiceNamePartial,resourceGuid,resourceSignature
    Sort Fields
        resourceId,tagServiceId,createTime,updateTime
    Supports Pagination


> Need to add pagination support and searchFilters for tag related APIs
> -
>
> Key: RANGER-4630
> URL: https://issues.apache.org/jira/browse/RANGER-4630
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Anand Nadar
>Priority: Minor
> Fix For: 3.0.0
>
>
> Currently for Tag related GET-APIs i.e for 
> (RangerTags,RangerTagDefs,RangerServiceResource) we dont support 
> pagination,and also we need additional searchFilters for them
>  
> 1) Tags
>     Request > /service/tags/tags/paginated?
> Supported Query Params 
>     Search Fields
>         tagId,tagDefId,tagType,tagTypePartial
>         multiple tagId search
>     Sort Fields
>         tagId,tagDefId,createTime,updateTime
>     Supports Pagination
> 2) TagDefs
>     Request > /service/tags/tagdefs/paginated?
> Supported Query Params 
>     Search Fields
> tagDefId,tagDefGuid,tagType,tagTypePartial,tagSource,
> tagSourcePartial
>     Sort Fields
>         tagDefId,tagType,createTime,updateTime
>     Supports Pagination
> 3) ServiceResource
>     Request > /service/tags/resources/paginated?
> Supported Query Params 
>     Search Fields
> resourceId,tagServiceId,tagServiceName,tagServiceNamePartial,resourceGuid,resourceSignature
> multiple resourceId search
>     Sort Fields
>         resourceId,tagServiceId,createTime,updateTime
>     Supports Pagination
> 4) TagResourceMaps
> Request => service/tags/tagresourcemaps/paginated
> Search fields - tagId, resourceId, serviceName
> Supports pagination



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

Community Over Code Asia 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code Asia 2024 are now
open!

We will be supporting Community over Code Asia, Hangzhou, China
July 26th - 28th, 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this year's applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Friday, May 10th, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you to
apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Hangzhou, China in July, 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

Re: Review Request 74884: RANGER-4692: Sorting on the Ranger Admin - Plugin Status page by event(Download, Activation)

[Rakesh Gupta]

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

(Updated Feb. 20, 2024, 9:02 a.m.)


Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay 
Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, sanket 
shelar, Sailaja Polavarapu, and Velmurugan Periasamy.


Changes
---

Added Sorting by pluginIpAddress


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


Repository: ranger


Description
---

Currently there are different type like (Policy, Role, Tag, UserStore and GDS) 
on plugin status.

when we have plugins(large enough to accommodate in single page), It will be 
helpful to identify any out-of-sync plugins based on download times, sorting 
them by policyDownloadTime, tagDownloadTime, roleDownloadTime, 
userstoreDownloadTime and gdsDownloadTime.


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPluginInfo.java
 6d3d17d9e 
  security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql fa72ef2ea 
  security-admin/db/mysql/patches/073-create-view-plugin-info.sql PRE-CREATION 
  security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql 
772514610 
  security-admin/db/oracle/patches/067-create-view-plugin-info.sql PRE-CREATION 
  security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
e177d44d7 
  security-admin/db/postgres/patches/073-create-view-plugin-info.sql 
PRE-CREATION 
  
security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql 
32cfed7ae 
  security-admin/db/sqlanywhere/patches/067-create-view-plugin-info.sql 
PRE-CREATION 
  security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql 
831aad66d 
  security-admin/db/sqlserver/patches/067-create-view-plugin-info.sql 
PRE-CREATION 
  security-admin/src/main/java/org/apache/ranger/entity/XXPluginInfo.java 
a15d8d056 
  
security-admin/src/main/java/org/apache/ranger/service/RangerPluginInfoService.java
 9dc26ceb7 


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

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


Testing
---

I have verified that new columns have been successfully added to the 
x_plugin_info table(for fresh installment), through which we can now sort by 
event(Download,Activation).
I have tested and confirmed that data can be inserted into these new columns in 
upgrade scenario, through which we can now use them for sorting the data based 
on events(Download,Activation).


Thanks,

Rakesh Gupta

[jira] [Updated] (RANGER-4692) Sorting on the Ranger Admin - Plugin Status page by event(Download,Activation)

[Rakesh Gupta (Jira)]

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

Rakesh Gupta updated RANGER-4692:
-
Attachment: 0002-RANGER-4692.patch

> Sorting on the Ranger Admin - Plugin Status page by event(Download,Activation)
> --
>
> Key: RANGER-4692
> URL: https://issues.apache.org/jira/browse/RANGER-4692
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Reporter: Rakesh Gupta
>Assignee: Rakesh Gupta
>Priority: Major
> Attachments: 0002-RANGER-4692.patch
>
>
> Currently there are different type like (Policy, Role, Tag, UserStore and 
> GDS) on plugin status.
> when we have plugins(large enough to accommodate in single page), It will be 
> helpful to identify any out-of-sync plugins based on download times, sorting 
> them by policyDownloadTime, tagDownloadTime, roleDownloadTime, 
> userstoreDownloadTime and gdsDownloadTime.



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

[jira] [Updated] (RANGER-4692) Sorting on the Ranger Admin - Plugin Status page by event(Download,Activation)

[Rakesh Gupta (Jira)]

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

Rakesh Gupta updated RANGER-4692:
-
Attachment: (was: 0001-RANGER-4692.patch)

> Sorting on the Ranger Admin - Plugin Status page by event(Download,Activation)
> --
>
> Key: RANGER-4692
> URL: https://issues.apache.org/jira/browse/RANGER-4692
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Reporter: Rakesh Gupta
>Assignee: Rakesh Gupta
>Priority: Major
> Attachments: 0002-RANGER-4692.patch
>
>
> Currently there are different type like (Policy, Role, Tag, UserStore and 
> GDS) on plugin status.
> when we have plugins(large enough to accommodate in single page), It will be 
> helpful to identify any out-of-sync plugins based on download times, sorting 
> them by policyDownloadTime, tagDownloadTime, roleDownloadTime, 
> userstoreDownloadTime and gdsDownloadTime.



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