You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Weizisheng (Jira)" <ji...@apache.org> on 2023/04/14 02:25:00 UTC
[jira] [Closed] (IMPALA-11245) Inaccurate tips with 'select' on not exist table
[ https://issues.apache.org/jira/browse/IMPALA-11245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weizisheng closed IMPALA-11245.
-------------------------------
Resolution: Won't Fix
> Inaccurate tips with 'select' on not exist table
> ------------------------------------------------
>
> Key: IMPALA-11245
> URL: https://issues.apache.org/jira/browse/IMPALA-11245
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 4.0.0, Impala 3.4.0
> Reporter: Weizisheng
> Priority: Minor
> Labels: auto-deprioritized-minor
>
> {code:java}
> select count(1) from db.test;{code}
> Both database 'db' and table 'test' are not exist. This will get error "{_}AnalysisException: Could not resolve table reference: 'db.test'{_}".
> If enabled Ranger then get error "{_}AuthorizationException: User 'xx' does not have privileges to execute 'SELECT' on default.db{_}".
> Actually maybe "{_}Table does not exist: db.test{_}" is more friendly tip :) . Just like 'insert into db.test' gives error "{_}AnalysisException: Database does not exist: db{_}".
> [resolvePath|https://github.com/apache/impala/blob/c190966db932cf7b24881ce2213fd6f7d9192099/fe/src/main/java/org/apache/impala/analysis/Analyzer.java#L1237] source code here ignores table not exist exception, and the above two errors return to the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org