[IMPALA-10710] Log When Kudu Table Already Exists in HMS

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Epic Color: ghx-label-3
• Assignee: Unassigned
• Reporter: David Mollitor
• Created: 20/May/21 17:20
• Updated: 20/May/21 20:13

Description

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 applies only to IF NOT EXISTS statements.

Issue Links

• is related to: IMPALA-8984 Submit several same kudu table created query concurrently may result in table deleted in Kudu storage