You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (Jira)" <ji...@apache.org> on 2019/12/13 16:35:00 UTC

[jira] [Commented] (SENTRY-2540) Only use SELECT action for filter SHOW DATABASES and SHOW TABLES command based on configuration

    [ https://issues.apache.org/jira/browse/SENTRY-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995748#comment-16995748 ] 

Hadoop QA commented on SENTRY-2540:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12988808/SENTRY-2540.002.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: https://builds.apache.org/job/PreCommit-SENTRY-Build/4448/console

This message is automatically generated.

> Only use SELECT action for filter SHOW DATABASES and SHOW TABLES command based on configuration
> -----------------------------------------------------------------------------------------------
>
>                 Key: SENTRY-2540
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2540
>             Project: Sentry
>          Issue Type: Improvement
>            Reporter: Na Li
>            Assignee: Na Li
>            Priority: Major
>         Attachments: SENTRY-2540.001.patch, SENTRY-2540.002.patch, SENTRY-2540.002.patch
>
>
> When there are thousands of databases, SHOW DATABASES may take a really long time because SENTRY checks if user has any of the following privileges on that database for filtering out the database
>         DBModelAction.SELECT, DBModelAction.INSERT, DBModelAction.ALTER,
>         DBModelAction.CREATE, DBModelAction.DROP, DBModelAction.INDEX,
>         DBModelAction.LOCK
> To speedup the authorization checking for this case, Sentry can check only the select privilege for SHOW DATABASES and SHOW TABLES based on configuration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)