You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Xiaoxiang Yu (JIRA)" <ji...@apache.org> on 2019/07/25 06:40:00 UTC

[jira] [Issue Comment Deleted] (KYLIN-4111) drop table failed with no valid privileges after KYLIN-3857

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

Xiaoxiang Yu updated KYLIN-4111:
--------------------------------
    Comment: was deleted

(was: Hi, backtick is introduce in KYLIN-3700, and in KYLIN-3857, I add a switch to allow user to close backtick. That is, use kylin.source.hive.enable.quote=false in kylin.properties to turn off quote. (default value is true). 

)

> drop table failed with no valid privileges after KYLIN-3857
> -----------------------------------------------------------
>
>                 Key: KYLIN-4111
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4111
>             Project: Kylin
>          Issue Type: Bug
>            Reporter: Liu Shaohui
>            Assignee: Liu Shaohui
>            Priority: Major
>
> After KYLIN-3857, there will be quote ` around database and table.
> The drop table sql will be:
> {code:java}
> DROP TABLE IF EXISTS `kylin_onebox.kylin_intermediate_kylin_sales_cube_7be84be1_a153_07c4_3ce6_270e8d99ff85`;{code}
> Hive (1.2)with sentry will throw exception:
> {code:java}
> Error: Error while compiling statement: FAILED: HiveAccessControlException No valid privileges
>  Required privileges for this query: Server=server1->Db=`kylin_onebox->Table=kylin_intermediate_kylin_sales_cube_7be84be1_a153_07c4_3ce6_270e8d99ff85`->action=drop;
> Query log: http://zjy-hadoop-prc-ct14.bj:18201/log?qid=898c7878-a961-443d-b120-cca0e2667d15_f486bd16-4bbd-4014-a0a7-c2ebfdbe6668 (state=42000,code=40000)
> {code}
> The reason is that hive identify the databse be `kylin_onebox and table be: kylin_intermediate_kylin_sales_cube_7be84be1_a153_07c4_3ce6_270e8d99ff85`
> May be we can fix it in hive and sentry. Just create a jira to show this problem.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)