[IMPALA-8459] Cannot delete impala/kudu table if backing kudu table dropped with local catalog

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Impala 3.3.0
• Fix Version/s: Impala 3.3.0
• Component/s: Catalog
• Labels: kudu
• Target Version: Impala 3.3.0
• Epic Color: ghx-label-3
• Assignee: Todd Lipcon
• Reporter: Tim Armstrong
• Created: 26/Apr/19 00:46
• Updated: 21/Jun/19 18:03
• Resolved: 18/Jun/19 17:21

Description

test_delete_external_kudu_table and test_delete_managed_kudu_table fail with local catalog, e.g. with:

E   HiveServer2Error: LocalCatalogException: Error opening Kudu table 'testimpalakuduintegration_1715_p3r46w.ogslbjblgv', Kudu error: the table does not exist: table_name: "testimpalakuduintegration_1715_p3r46w.ogslbjblgv"

Issue Links

• Blocked: IMPALA-8594 Support drop table for external kudu tables that are dropped in kudu
• is related to: IMPALA-6343 Allow dropping of Kudu tables with invalid master addresses