You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "peng.jianhua (JIRA)" <ji...@apache.org> on 2017/10/09 03:47:00 UTC
[jira] [Updated] (RANGER-1796) Updated masking policy for hive to
support for deny/allowException/denyExceptions
[ https://issues.apache.org/jira/browse/RANGER-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
peng.jianhua updated RANGER-1796:
---------------------------------
Attachment: masking-04.png
> 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, masking-03.png, masking-04.png, masking2.png, usecase-01.png, usecase-02.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)