[IMPALA-8594] Support drop table for external kudu tables that are dropped in kudu

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: Impala 3.1.0
• Component/s: Catalog
• Epic Color: ghx-label-3
• Assignee: Unassigned
• Reporter: Manish Maheshwari
• Created: 29/May/19 09:40
• Updated: 30/May/19 04:40
• Resolved: 30/May/19 04:40

Description

External kudu tables in Impala cannot be dropped from HMS if the kudu table is already dropped in kudu. This cases HMS to be out of sync with kudu metadata.

Impala should clean up HMS table info when a drop is executed for an external table that does not exist in kudu

 

cc - balazsj_impala_220b tlipcon

Issue Links

• Blocked: IMPALA-8459 Cannot delete impala/kudu table if backing kudu table dropped with local catalog