You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sentry.apache.org by "Sravya Tirukkovalur (JIRA)" <ji...@apache.org> on 2014/08/04 22:58:13 UTC

[jira] [Updated] (SENTRY-74) Add column-level privileges for Hive/Impala

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

Sravya Tirukkovalur updated SENTRY-74:
--------------------------------------

    Fix Version/s: 1.5.0

> 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
>             Fix For: 1.5.0
>
>
> 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)