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

Madhan Neethiraj commented on RANGER-3765:
------------------------------------------

Thanks [~rmani]. I cherry-picked this commit into ranger-2.3 branch:
{noformat}
commit 3bb5c083856f09de16dabd3e2ee5de29e746f420 (HEAD -> ranger-2.3, 
origin/ranger-2.3)
Author: Madhan Neethiraj <[email protected]>
Date:   Mon May 16 12:13:45 2022 -0700

    RANGER-3765: tag-based policy masking to override resource-based masking

    (cherry picked from commit fbe203b55e29716fde3b037aeb336ebbae6c5cd2)
 {noformat}

> tag-based policy masking to override resource-based policy
> ----------------------------------------------------------
>
>                 Key: RANGER-3765
>                 URL: https://issues.apache.org/jira/browse/RANGER-3765
>             Project: Ranger
>          Issue Type: Bug
>          Components: plugins
>    Affects Versions: 3.0.0, 2.3.0
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: RANGER-3765.patch
>
>
> 1. consider following two masking policies - one tag-based policy and the 
> other resource-based:
> {noformat}
> tag-based policy:
>   id: 1, tag: TAG1,
>     users: [ user1 ], maskType: MASK_NULL
> resource-based policy:
>   id: 2, database: db1, table: tbl1, column: col1,
>     users: [ user1 ], maskType: MASK_SHOW_LAST_4{noformat}
> 2. consider that column {{db1.tbl1.col1}} has tag {{{}TAG1{}}}.
> When {{user1}} accesses table {{{}db1.tbl1{}}}, the value of column {{col1}} 
> should be masked as specified in tag-based policy id=1; however, mask 
> specified in resource-based policy id=2 is applied instead. This should be 
> updated to choose the mask specified in tag-based policy when both tag-based 
> and resource-based policies have same priority.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to