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

peng.jianhua updated RANGER-1796:
---------------------------------
    Description: 
Masking policy for hive  should support for deny/allowException/denyExceptions 
to meet further business needs. Such as masking policy for hive should support 
as following scene and so on:
USER1, USER2 and USER3 belong to the user group GROUPA. Select GROUPA group 
when created masking policy. The USER1 does not use masking and USER2, USER3 
need masking.

We rigorously tested this issue. The test result shows that the feature is ok.

  was:
Masking policy for hive  should support for deny/allowException/denyExceptions 
to meet further business needs. Such as masking policy for hive should support 
as following scene and so on:
USER1, USER2 and USER3 belong to the user group GROUPA. Select GROUPA group 
when created masking policy. The USER1 does not use masking and USER2, USER3 
need masking.


> Updated masking policy for hive  to support for 
> deny/allowException/denyExceptions
> ----------------------------------------------------------------------------------
>
>                 Key: RANGER-1796
>                 URL: https://issues.apache.org/jira/browse/RANGER-1796
>             Project: Ranger
>          Issue Type: New Feature
>          Components: plugins
>    Affects Versions: 1.0.0, master
>            Reporter: peng.jianhua
>            Assignee: peng.jianhua
>              Labels: newbie, patch
>         Attachments: 
> 0001-RANGER-1796-Updated-masking-policy-for-hive-to-suppo.patch, masking2.png
>
>
> Masking policy for hive  should support for 
> deny/allowException/denyExceptions to meet further business needs. Such as 
> masking policy for hive should support as following scene and so on:
> USER1, USER2 and USER3 belong to the user group GROUPA. Select GROUPA group 
> when created masking policy. The USER1 does not use masking and USER2, USER3 
> need masking.
> We rigorously tested this issue. The test result shows that the feature is ok.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to