[
https://issues.apache.org/jira/browse/IMPALA-9717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on IMPALA-9717 started by wuchang.
---------------------------------------
> Table Not Found Already Happened after Table Already Exists
> -----------------------------------------------------------
>
> Key: IMPALA-9717
> URL: https://issues.apache.org/jira/browse/IMPALA-9717
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.12.0
> Reporter: wuchang
> Assignee: wuchang
> Priority: Major
> Attachments: image-2020-05-02-10-38-03-250.png,
> image-2020-05-02-10-38-36-216.png
>
>
> I tried to create a already-existing tables in impala clusters, impala
> reports normal `Table Already Exists` error. But when I try to drop the
> table, it reports weird `Table does not exist`:
> {code:java}
> 0: jdbc:hive2://bronze-impala:2> CREATE TABLE IF NOT EXISTS
> hawkeye_alert_test_1488005975517 (id INT, ts BIGINT);
> Table already exists
> +----------+--+
> | summary |
> +----------+--+
> +----------+--+
> No rows selected (1.96 seconds)
> 0: jdbc:hive2://bronze-impala:2> drop table hawkeye_alert_test_1488005975517;
> Error: AnalysisException: Table does not exist:
> default.hawkeye_alert_test_1488005975517 (state=HY000,code=0)
> {code}
>
> It could be re-produced easily;
> The root cause is that when `table already exists` happened in
> CatalogOpExecutor, catalog didn't setup the catalog version, instead, a
> version 0 is set by default in TCatalogUpdateResult
> !image-2020-05-02-10-38-36-216.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
