[
https://issues.apache.org/jira/browse/SENTRY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702367#comment-14702367
]
Hadoop QA commented on SENTRY-716:
----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12751152/SENTRY-716.patch
against master.
{color:red}Overall:{color} -1 due to 3 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.tests.e2e.dbprovider.TestDbOperations
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.hive.TestOperations
Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/801/console
This message is automatically generated.
> Hive pluing does not correctly enforce privileges for new in case of nested
> queries
> -----------------------------------------------------------------------------------
>
> Key: SENTRY-716
> URL: https://issues.apache.org/jira/browse/SENTRY-716
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Prasad Mujumdar
> Attachments: SENTRY-716.patch
>
>
> A nested query on view incorrectly enforces base table privileges instead of
> view privileges. For example,
> {noformat}
> create view v1 as select * from t1;
> grant select on table v1 to role test;
> select * from ( select * from v1) v2;
> {noformat}
> doesn't work if you have read privilege on view v1. It only works when you
> have read privilege on underlying table t1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
