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


Ship it!




Ship It!

- Madhan Neethiraj


On Feb. 7, 2024, 1:49 p.m., sanket shelar wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74865/
> -----------------------------------------------------------
> 
> (Updated Feb. 7, 2024, 1:49 p.m.)
> 
> 
> Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay 
> Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Sailaja 
> Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4690
>     https://issues.apache.org/jira/browse/RANGER-4690
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> Create a ranger hive policy for user u1 to access table t1.
> Create table t1 and add data
> Edit the policy to have multiple versions. Polocy version is now 'y'
> Create a ranger hive masking policy for one of the columns of t1.
> Edit the policy to have multiple versions. Policy version is less than 'y'
> example, if resource policy version is 5, have masking policy version as 4.
> Try insert command on t1. It fails now as there is a masking policy.
> Inspect access audits on ranger admin UI. Click on policyid for the denied 
> audit for insert
> 
> CURRENT BEHAVIOUR:
> Access audits show version of resource policy for mask policy id, so querying 
> for policy details leads to data not found error page
> 
> Policy cache json file on plugin side has the right version, x_policy table 
> has the right entries for corresponding masking policy
> 
> 
> Diffs
> -----
> 
>   
> hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java
>  44c66dfd9 
> 
> 
> Diff: https://reviews.apache.org/r/74865/diff/1/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> sanket shelar
> 
>

Reply via email to