[jira] [Updated] (SENTRY-687) Handle authorization for 'select ' hive queries

["Prasad Mujumdar (JIRA)" <ji...@apache.org>]

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

Prasad Mujumdar updated SENTRY-687:
-----------------------------------
    Description: 
Hive internally rewrites this 'select <expression>' query into 'select <expression> from _dummy_database._dummy_table', where these dummy db and table are temp entities for the current query.
The Hive binding need to handle these special objects.


  was:
Hive internally rewrites this 'select <expression>' query into 'select <expression> from _dummy_database._dummy_table', where these dummy db and table are temp entities for the current query.
The Hive binding need to handle these special objects. 
Perhaps a long term solution would be for Hive compiler to identify the special objects which the auth plugins should skip. In short term we can just allow access to "_dummy_database" implicitly.


> Handle authorization for 'select <expr>' hive queries
> -----------------------------------------------------
>
>                 Key: SENTRY-687
>                 URL: https://issues.apache.org/jira/browse/SENTRY-687
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: Prasad Mujumdar
>
> Hive internally rewrites this 'select <expression>' query into 'select <expression> from _dummy_database._dummy_table', where these dummy db and table are temp entities for the current query.
> The Hive binding need to handle these special objects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)