[jira] [Updated] (RANGER-4617) Need to add ACL principal details in dataset summary API

[Prashant Satam (Jira)]

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

Prashant Satam updated RANGER-4617:
---
Description: 
Currently in dataset-summary API we have a field 
"principalsCount" which gives details of principal in dataset policy ,Also 
adding field "aclPrincipalsCount" which will give details of principals in 
dataset ACL will also be helpful for getting more information for a dataset 

> Need to add ACL principal details in dataset summary API 
> -
>
> Key: RANGER-4617
> URL: https://issues.apache.org/jira/browse/RANGER-4617
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>
> Currently in dataset-summary API we have a field 
> "principalsCount" which gives details of principal in dataset policy ,Also 
> adding field "aclPrincipalsCount" which will give details of principals in 
> dataset ACL will also be helpful for getting more information for a dataset 



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

[jira] [Created] (RANGER-4617) Need to add ACL principal details in dataset summary API

[Prashant Satam (Jira)]

Prashant Satam created RANGER-4617:
--

 Summary: Need to add ACL principal details in dataset summary API 
 Key: RANGER-4617
 URL: https://issues.apache.org/jira/browse/RANGER-4617
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Prashant Satam






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

[jira] [Assigned] (RANGER-4617) Need to add ACL principal details in dataset summary API

[Prashant Satam (Jira)]

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

Prashant Satam reassigned RANGER-4617:
--

Assignee: Prashant Satam

> Need to add ACL principal details in dataset summary API 
> -
>
> Key: RANGER-4617
> URL: https://issues.apache.org/jira/browse/RANGER-4617
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Prashant Satam
>Assignee: Prashant Satam
>Priority: Major
>




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

[PR] RANGER-4619:Change the http client of the knox plug-in to avoid conne… [ranger]

[via GitHub]

upczsh opened a new pull request, #293:
URL: https://github.com/apache/ranger/pull/293

   …ctivity failure caused by SSL links.
   
   ## What changes were proposed in this pull request?
   
   The ranger knox plug-in will report SSLHandhakeException during the 
connectivity test. SSL should not be required for the plug-in, so the http 
client is changed to avoid errors caused by the SSL handshake.
   The error is reported as follows：
   
![c1e0a9bbd1df74af13c253d5711cfd0f.png](file:///Users/zhaoshuaihua/.config/joplin-desktop/resources/b6f50341946e46deb31e688ef63a21a1.png)
   
![b855a1de75f10e8f5b026e6ecad40a22.png](file:///Users/zhaoshuaihua/.config/joplin-desktop/resources/122e5a9ba6a6419fb8288bd4e3c99ea2.png)
   
   ## How was this patch tested?
   After changing the http client, the test is as follows:
   
![bfe86186d9630289532d1c91274faceb.png](file:///Users/zhaoshuaihua/.config/joplin-desktop/resources/472b1bb5d0b94897abfe8e3ad9212d76.png)
   
![2d042ac2720bf5659656c19b9d396dc4.png](file:///Users/zhaoshuaihua/.config/joplin-desktop/resources/4e5355daaeb3449eaba16e617b729a1f.png)
   
![26ea570871a4793fd0de935018238fc1.png](file:///Users/zhaoshuaihua/.config/joplin-desktop/resources/46e01847ea224760a24e205fc4b7679c.png)
   
![921ada850bae4a34b139973c534b162b.png](file:///Users/zhaoshuaihua/.config/joplin-desktop/resources/f0c7fdfc7e3f4ba89173b1e46efffd4d.png)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Review Request 74753: RANGER-4521: All records not displayed on Admin Audits UI when filtered using session ID

[Kishor Gollapalliwar]

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




security-admin/src/main/java/org/apache/ranger/service/XTrxLogService.java
Line 111 (original), 106 (patched)


Please handle scenario when session is null



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


What will happen if session is null ?


- Kishor Gollapalliwar


On Dec. 14, 2023, 7:26 a.m., Rakesh Gupta wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74753/
> ---
> 
> (Updated Dec. 14, 2023, 7:26 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.
> 
> 
> Bugs: RANGER-4521
> https://issues.apache.org/jira/browse/RANGER-4521
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Some audit entries for keyadmin user are missing when filtered using 
> sessionID or Audit Type = Ranger Policy. Also when moved to next page most 
> audit entries are missing
> 
> (Audits for import and export are shown, audit corresponding to policy crud 
> operation is missing for keyadmin user)
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/service/XTrxLogService.java 
> 9d9e0bbc0 
> 
> 
> Diff: https://reviews.apache.org/r/74753/diff/4/
> 
> 
> Testing
> ---
> 
> Tested All audits are displayed properly with filter and without filter for 
> admin and keyadmin user.
> 
> 
> Thanks,
> 
> Rakesh Gupta
> 
>

Re: Review Request 74657: RANGER-4467: User Agent info not logged under "Login sessions" when login fails

[Kishor Gollapalliwar]

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


Ship it!




Ship It!

- Kishor Gollapalliwar


On Oct. 10, 2023, 11:03 a.m., Rakesh Gupta wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74657/
> ---
> 
> (Updated Oct. 10, 2023, 11:03 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.
> 
> 
> Bugs: RANGER-4467
> https://issues.apache.org/jira/browse/RANGER-4467
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> User Agent info missing when login fails. Its good to display this detail as 
> it helps in knowing how the login was tried in case of failed login attempts
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/SessionMgr.java 
> 89bffa7c9 
>   
> security-admin/src/main/java/org/apache/ranger/security/listener/SpringEventListener.java
>  8f46af968 
>   
> security-admin/src/main/java/org/apache/ranger/security/web/authentication/RangerAuthSuccessHandler.java
>  52cf17ae1 
> 
> 
> Diff: https://reviews.apache.org/r/74657/diff/1/
> 
> 
> Testing
> ---
> 
> Provided wrong uname or password on Ranger admin UI so that login fails.
> Verified login sessions under Audits page that User Agent info is displayed 
> for Wrong Username/Password
> 
> 
> Thanks,
> 
> Rakesh Gupta
> 
>

Re: Review Request 74788: RANGER:4603 : Need to add query param createdBy for dataset GET API

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On Dec. 13, 2023, 11:35 a.m., Prashant Satam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74788/
> ---
> 
> (Updated Dec. 13, 2023, 11:35 a.m.)
> 
> 
> Review request for ranger, Akshay Tupe, Anand Nadar, Ankita Sinha, Madhan 
> Neethiraj, Monika Kachhadiya, Subhrat Chaudhary, and Vanita Ubale.
> 
> 
> Bugs: RANGER-4603
> https://issues.apache.org/jira/browse/RANGER-4603
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Currently we have dataset GET APIs to get list datasets based on ACL. It will 
> be useful to be able filter the list based on users who created the dataset, 
> especially to get the datasets created by self.
> 
> 
> Diffs
> -
> 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
> 719ec3005 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> af70daa9d 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> 87a278674 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerGdsDatasetService.java
>  e8d672015 
> 
> 
> Diff: https://reviews.apache.org/r/74788/diff/2/
> 
> 
> Testing
> ---
> 
> Steps to check 
> 1)create 2 users with userName user1,user2
> 2)create 1 dataset by user 1 and add user 2 in dataset ACL with permission 
> VIEW
> 3)use GET API (service/gds/dataset) with query param createdBy we will get 
> dataset in response
> 4)Request ==> (service/gds/dataset?createdBy=user2)
> 
> 
> Thanks,
> 
> Prashant Satam
> 
>

Re: Review Request 74790: RANGER-4604: Need to add query param createdBy for security-zone GET API

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On Dec. 13, 2023, 11:52 a.m., Prashant Satam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74790/
> ---
> 
> (Updated Dec. 13, 2023, 11:52 a.m.)
> 
> 
> Review request for ranger, Akshay Tupe, Anand Nadar, Ankita Sinha, Madhan 
> Neethiraj, Monika Kachhadiya, Subhrat Chaudhary, and Vanita Ubale.
> 
> 
> Bugs: RANGER-4604
> https://issues.apache.org/jira/browse/RANGER-4604
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> We need to add a query param createdBy for security-zone GET API. It will be 
> useful to filter list of security-zones created by user, especially to get 
> the security-zone created by self
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/SecurityZonePredicateUtil.java
>  54b477502 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
> 719ec3005 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> 87a278674 
> 
> 
> Diff: https://reviews.apache.org/r/74790/diff/1/
> 
> 
> Testing
> ---
> 
> Steps to test
> 1)create a Security-zone by Test-user-1
> 2)GET security-zones using GET API /service/zones/zones by using query param 
> createdBy
> 3)Request > (/service/zones/zones?createdBy=Test-user-1) in Response you 
> will get zones which are created by Test-user-1
> 
> 
> Thanks,
> 
> Prashant Satam
> 
>

Re: Review Request 74657: RANGER-4467: User Agent info not logged under "Login sessions" when login fails

[Pradeep Agrawal]

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


Ship it!




Ship It!

- Pradeep Agrawal


On Oct. 10, 2023, 11:03 a.m., Rakesh Gupta wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74657/
> ---
> 
> (Updated Oct. 10, 2023, 11:03 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.
> 
> 
> Bugs: RANGER-4467
> https://issues.apache.org/jira/browse/RANGER-4467
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> User Agent info missing when login fails. Its good to display this detail as 
> it helps in knowing how the login was tried in case of failed login attempts
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/SessionMgr.java 
> 89bffa7c9 
>   
> security-admin/src/main/java/org/apache/ranger/security/listener/SpringEventListener.java
>  8f46af968 
>   
> security-admin/src/main/java/org/apache/ranger/security/web/authentication/RangerAuthSuccessHandler.java
>  52cf17ae1 
> 
> 
> Diff: https://reviews.apache.org/r/74657/diff/1/
> 
> 
> Testing
> ---
> 
> Provided wrong uname or password on Ranger admin UI so that login fails.
> Verified login sessions under Audits page that User Agent info is displayed 
> for Wrong Username/Password
> 
> 
> Thanks,
> 
> Rakesh Gupta
> 
>

[PR] RANGER-4618:property ranger.accesslog.rotate.rename_on_rotate, the de… [ranger]

[via GitHub]

upczsh opened a new pull request, #292:
URL: https://github.com/apache/ranger/pull/292

   …fault value is false, not 15
   
   ## What changes were proposed in this pull request?
   
   Fix the default value of ranger.accesslog.rotate.rename_on_rotate 
configuration in ranger--admin-default-site.xml. The default value of this 
configuration is false instead of 15.
   
![image](https://github.com/apache/ranger/assets/50791733/4dbadd0b-0c89-411f-84bf-9f173dcdfd4c)
   
![image](https://github.com/apache/ranger/assets/50791733/a72f6e18-fcee-4f8d-8155-fa7cb9eb76e4)
   
   ## How was this patch tested?
   
   (Please explain how this patch was tested. Ex: unit tests, manual tests)
   (If this patch involves UI changes, please attach a screen-shot; otherwise, 
remove this)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Assigned] (RANGER-4615) Keep the LDAP usersync details popup names same as the backbone js names

[Abhishek (Jira)]

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

Abhishek reassigned RANGER-4615:


Assignee: Mugdha Varadkar  (was: Abhishek)

> Keep the LDAP usersync details popup names same as the backbone js names
> 
>
> Key: RANGER-4615
> URL: https://issues.apache.org/jira/browse/RANGER-4615
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Harshal Chavan
>Assignee: Mugdha Varadkar
>Priority: Major
>
> The data field names are different in the usersync audits sync details popup 
> in ReactJS when compared to backbone JS.
> Ideally, both BackBone JS and React JS field names should be the same.



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

[jira] [Assigned] (RANGER-4615) Keep the LDAP usersync details popup names same as the backbone js names

[Abhishek (Jira)]

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

Abhishek reassigned RANGER-4615:


Assignee: Abhishek  (was: Mugdha Varadkar)

> Keep the LDAP usersync details popup names same as the backbone js names
> 
>
> Key: RANGER-4615
> URL: https://issues.apache.org/jira/browse/RANGER-4615
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Harshal Chavan
>Assignee: Abhishek
>Priority: Major
>
> The data field names are different in the usersync audits sync details popup 
> in ReactJS when compared to backbone JS.
> Ideally, both BackBone JS and React JS field names should be the same.



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

[jira] [Created] (RANGER-4616) Updated to committer info

[Selvamohan Neethiraj (Jira)]

Selvamohan Neethiraj created RANGER-4616:


 Summary: Updated to committer info
 Key: RANGER-4616
 URL: https://issues.apache.org/jira/browse/RANGER-4616
 Project: Ranger
  Issue Type: Task
  Components: documentation
Reporter: Selvamohan Neethiraj
Assignee: Selvamohan Neethiraj






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

[jira] [Created] (RANGER-4615) Keep the LDAP usersync details popup names same as the backbone js names

[Harshal Chavan (Jira)]

Harshal Chavan created RANGER-4615:
--

 Summary: Keep the LDAP usersync details popup names same as the 
backbone js names
 Key: RANGER-4615
 URL: https://issues.apache.org/jira/browse/RANGER-4615
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Harshal Chavan


The data field names are different in the usersync audits sync details popup in 
ReactJS when compared to backbone JS.
Ideally, both BackBone JS and React JS field names should be the same.



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

[jira] [Assigned] (RANGER-4615) Keep the LDAP usersync details popup names same as the backbone js names

[Harshal Chavan (Jira)]

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

Harshal Chavan reassigned RANGER-4615:
--

Assignee: Mugdha Varadkar

> Keep the LDAP usersync details popup names same as the backbone js names
> 
>
> Key: RANGER-4615
> URL: https://issues.apache.org/jira/browse/RANGER-4615
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Harshal Chavan
>Assignee: Mugdha Varadkar
>Priority: Major
>
> The data field names are different in the usersync audits sync details popup 
> in ReactJS when compared to backbone JS.
> Ideally, both BackBone JS and React JS field names should be the same.



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

[jira] [Updated] (RANGER-4610) API calls for zones and services on initial landing in ZoneListing page is being called twice

[Brijesh Bhalala (Jira)]

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

Brijesh Bhalala updated RANGER-4610:

Attachment: 0002-RANGER-4610.patch

> API calls for zones and services on initial landing in ZoneListing page is 
> being called twice
> -
>
> Key: RANGER-4610
> URL: https://issues.apache.org/jira/browse/RANGER-4610
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Attachments: 0001-RANGER-4610.patch, 0002-RANGER-4610.patch
>
>
> API calls for zones and services on initial landing in ZoneListing page is 
> being called twice.
> *Actual :-*
> * On initial landing in ZoneListing page, the API calls for zones & services 
> are being called twice.
> *Expected :-*
> * On initial landing in ZoneListing page, the API calls for zones & services 
> should get called only once.
>  



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

[jira] [Updated] (RANGER-4614) GDS : Need new apis to get audit history of dataset/datashare

[Anand Nadar (Jira)]

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

Anand Nadar updated RANGER-4614:

Description: 
Need api to get the audit log of a particular dataset/datashare.

Dataset history should contain
 1. Changes on dataset object
 2. Change on dataset policy
 3. Changes on DatashareInDataset object. 

Datashare history should contain
 1. Changes on Datashare object.
 2. Changes on its SharedResources.

> GDS : Need new apis to get audit history of dataset/datashare
> -
>
> Key: RANGER-4614
> URL: https://issues.apache.org/jira/browse/RANGER-4614
> Project: Ranger
>  Issue Type: Task
>  Components: admin
>Reporter: Anand Nadar
>Priority: Major
>
> Need api to get the audit log of a particular dataset/datashare.
> Dataset history should contain
>  1. Changes on dataset object
>  2. Change on dataset policy
>  3. Changes on DatashareInDataset object. 
> Datashare history should contain
>  1. Changes on Datashare object.
>  2. Changes on its SharedResources.



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

[jira] [Created] (RANGER-4614) GDS : Need new apis to get audit history of dataset/datashare

[Anand Nadar (Jira)]

Anand Nadar created RANGER-4614:
---

 Summary: GDS : Need new apis to get audit history of 
dataset/datashare
 Key: RANGER-4614
 URL: https://issues.apache.org/jira/browse/RANGER-4614
 Project: Ranger
  Issue Type: Task
  Components: admin
Reporter: Anand Nadar






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

[jira] [Updated] (RANGER-4610) API calls for zones and services on initial landing in ZoneListing page is being called twice

[Brijesh Bhalala (Jira)]

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

Brijesh Bhalala updated RANGER-4610:

Attachment: 0001-RANGER-4610.patch

> API calls for zones and services on initial landing in ZoneListing page is 
> being called twice
> -
>
> Key: RANGER-4610
> URL: https://issues.apache.org/jira/browse/RANGER-4610
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
>  Labels: ranger-react
> Attachments: 0001-RANGER-4610.patch
>
>
> API calls for zones and services on initial landing in ZoneListing page is 
> being called twice.
> *Actual :-*
> * On initial landing in ZoneListing page, the API calls for zones & services 
> are being called twice.
> *Expected :-*
> * On initial landing in ZoneListing page, the API calls for zones & services 
> should get called only once.
>  



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

[jira] [Updated] (RANGER-4613) GDS : Need filter of objectId in /assets/report api to filter out history specific to a dataset/datashare

[Madhan Neethiraj (Jira)]

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

Madhan Neethiraj updated RANGER-4613:
-
Attachment: RANGER-4613.patch

> GDS : Need filter of objectId in /assets/report api to filter out history 
> specific to a dataset/datashare
> -
>
> Key: RANGER-4613
> URL: https://issues.apache.org/jira/browse/RANGER-4613
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Reporter: Anand Nadar
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4613.patch
>
>
> We are creating a tab inside dataset/datashare detail layout to should the 
> history of changes done in that particular dataset/datashare.
> The current api - /assets/report only filters the result on the basic of 
> objectClassType which will give result of all datasets/datashare history.
> Therefore we need an additional filter of objectId, and then we can use 
> objectClassType and objectId together to filter out the history of a 
> particular dataset/datashare.



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

Review Request 74796: RANGER-4613: updated trx log retrieval API to support objectId query param

[Madhan Neethiraj]

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

Review request for ranger, Anand Nadar, Ankita Sinha, Abhay Kulkarni, Mehul 
Parikh, Mugdha Varadkar, Ramesh Mani, and Subhrat Chaudhary.


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


Repository: ranger


Description
---

- updated REST API at /service/assets/report to support objectId query param, 
to return only trx log for a given object


Diffs
-

  security-admin/src/main/java/org/apache/ranger/rest/AssetREST.java abc324dd1 
  security-admin/src/main/java/org/apache/ranger/service/XTrxLogService.java 
9d9e0bbc0 


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


Testing
---

- verified that response from /service/assets/report includes only the trx log 
for the object specified in query-param objectId


Thanks,

Madhan Neethiraj

[jira] [Assigned] (RANGER-4613) GDS : Need filter of objectId in /assets/report api to filter out history specific to a dataset/datashare

[Madhan Neethiraj (Jira)]

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

Madhan Neethiraj reassigned RANGER-4613:


Assignee: Madhan Neethiraj

> GDS : Need filter of objectId in /assets/report api to filter out history 
> specific to a dataset/datashare
> -
>
> Key: RANGER-4613
> URL: https://issues.apache.org/jira/browse/RANGER-4613
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Reporter: Anand Nadar
>Assignee: Madhan Neethiraj
>Priority: Major
>
> We are creating a tab inside dataset/datashare detail layout to should the 
> history of changes done in that particular dataset/datashare.
> The current api - /assets/report only filters the result on the basic of 
> objectClassType which will give result of all datasets/datashare history.
> Therefore we need an additional filter of objectId, and then we can use 
> objectClassType and objectId together to filter out the history of a 
> particular dataset/datashare.



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