[
https://issues.apache.org/jira/browse/SENTRY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523687#comment-14523687
]
Prasad Mujumdar commented on SENTRY-716:
----------------------------------------
The behavior is likely due to Hive compiler query rewrite setting view and
table entities differently in case of nested queries.
> 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
>
> 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)
