You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/10/03 16:07:00 UTC
[jira] [Commented] (SENTRY-1957) Do not parse hive sql string in
Sentry
[ https://issues.apache.org/jira/browse/SENTRY-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189910#comment-16189910 ]
Na Li commented on SENTRY-1957:
-------------------------------
The issues we found for auth-2 when integrating with Hive are:
1. When dropping non-exist database, hive does not pass name of the non-exist database to DefaultSentryValidator.checkPrivileges(). It seems it is hard for hive to fix it.
2. When dropping non-exist table, hive does not pass name of the non-exist table to DefaultSentryValidator.checkPrivileges(). It seems it is hard for hive to fix it.
3. When creating or dropping function, hive does not pass class name of the function. HIVE-17544 is fixing this issue.
> Do not parse hive sql string in Sentry
> --------------------------------------
>
> Key: SENTRY-1957
> URL: https://issues.apache.org/jira/browse/SENTRY-1957
> Project: Sentry
> Issue Type: Task
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: Na Li
> Assignee: Na Li
> Attachments: SENTRY-1957.002.patch, SENTRY-1957.003.patch
>
>
> In current authorization 2 API, Hive does not provide parsed sql string to Sentry. So sentry parses the sql string to get database name and table name.
> Once the API changes to include the parsed sql string, sentry should remove the code that parses the sql string in SimpleSemanticAnalyzer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)