sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tuong Truong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-74) Add column-level privileges for Hive/Impala
Date Thu, 14 Aug 2014 15:52:12 GMT

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

Tuong Truong commented on SENTRY-74:
------------------------------------

Hi  [~dapengsun],

Yike,  having to do it for individual column is not user friendly.   A typical BigData table
may have hundreds of columns; it will be a pain to deal with multiple columns in this manner.
 It probably more useful to enhance the policy parser to handle multiple column specification.
  It's more likely that a user is blocked access a small subset of the columns to protect
some sensitive data while allow access to the rest.

> Add column-level privileges for Hive/Impala
> -------------------------------------------
>
>                 Key: SENTRY-74
>                 URL: https://issues.apache.org/jira/browse/SENTRY-74
>             Project: Sentry
>          Issue Type: Improvement
>    Affects Versions: 1.3.0
>            Reporter: Jeremy Beard
>            Assignee: Dapeng Sun
>             Fix For: 1.5.0
>
>         Attachments: Design Document of Column-Level Access Control_v1.pdf
>
>
> Currently the finest grain of privilege is at the table/view level. This leads to the
unwieldy scenario where a different view has to be created for each combination of columns
that need to be restricted. With column level privileges this would not be required.
> In the policy file column privileges might potentially look like:
> server=server1->db=default->table=employees->column=salary->action=select



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message