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 "David Mollitor (Jira)" <ji...@apache.org> on 2021/05/20 17:21:00 UTC
[jira] [Created] (IMPALA-10710) Do Not Drop Kudu Table When Table
Already Exists
David Mollitor created IMPALA-10710:
---------------------------------------
Summary: Do Not Drop Kudu Table When Table Already Exists
Key: IMPALA-10710
URL: https://issues.apache.org/jira/browse/IMPALA-10710
Project: IMPALA
Issue Type: Bug
Reporter: David Mollitor
As I understand the code, Impala performs HMS/Kudu {{CREATE TABLE}} interaction as:
* Create the table in Kudu
* Register table with HMS
* Drop the Kudu table on HMS error
This is generally OK, except that it drops the table from Kudu on a {{TableAlreadyExists}} Exception.
So, if I issue the same {{CREATE TABLE}} statement twice, the data will be dropped from Kudu on the second execution.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org