sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Mujumdar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-74) Add column-level privileges for Hive/Impala
Date Sun, 05 Oct 2014 18:55:34 GMT

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

Prasad Mujumdar commented on SENTRY-74:
---------------------------------------

I think we are pretty close to getting this committed. Here are a few minor things left -
- Take another pass at the review comments and make sure the updated patches are attached
to the ticket.
- Rebase the patch on latest
- Regenerate the thrift code after rebase since some of the interfaces are changed on the
master branch

> 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.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)

Mime
View raw message