[
https://issues.apache.org/jira/browse/SENTRY-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108659#comment-14108659
]
SentryQA commented on SENTRY-74:
--------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12663639/SENTRY-74.patch
against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to build with patch (exit code 1)
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-SENTRY-Build/267/console
This message is automatically generated.
> 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.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.2#6252)
