[IMPALA-9030] Handle translated external Kudu tables

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 3.4.0
• Epic Color: ghx-label-1
• Assignee: Vihang Karajgaonkar
• Reporter: Vihang Karajgaonkar
• Created: 09/Oct/19 01:06
• Updated: 04/Nov/19 23:15
• Resolved: 04/Nov/19 23:15

Description

In HIVE-22158 HMS disallows creating of any managed table which is not transactional. This breaks the behavior for managed Kudu tables created from Impala. When user creates a managed Kudu table, HMS internally translates such table into a external table with an additional property "TRANSLATED_TO_EXTERNAL" set to true. The table type is changed to EXTERNAL.

Subsequently, when such a table is dropped or renamed, Catalog thinks such tables as external and does not update Kudu (dropping the table in Kudu or renaming the table in Kudu). This is unexpected from the point of view of user since user may think that they created a managed table and Impala should handle the drop and rename accordingly. The same applies to certain other alter operations like alter table set properties on a managed Kudu table which previously was disallowed now goes through after HIVE-22158

Issue Links

• is caused by: HIVE-22158 HMS Translation layer - Disallow non-ACID MANAGED tables.