ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "peng.jianhua (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-1796) Updated masking policy for hive to support for deny/allowException/denyExceptions
Date Tue, 26 Sep 2017 09:08:00 GMT

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

peng.jianhua commented on RANGER-1796:

Hi [~madhan.neethiraj], the case you mentioned can be handled. The feature will not affect
the existing function, it is the enhancement and improvement for the existing function.  These
existing functions have no effect after joined this issue. It allows Ranger to support features
that were not previously supported.

> 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, usecase-01.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

View raw message