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

Dapeng Sun updated SENTRY-74:
-----------------------------
    Attachment: SENTRY-74.006.patch

> 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, SENTRY-74.003.patch, SENTRY-74.004.patch, SENTRY-74.005.patch, SENTRY-74.006.patch, SENTRY-74.2.patch, SENTRY-74.patch
>
>
> 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.3.4#6332)