[jira] [Created] (IMPALA-9030) Handle translated external Kudu tables

["Vihang Karajgaonkar (Jira)" <ji...@apache.org>]

Vihang Karajgaonkar created IMPALA-9030:
-------------------------------------------

             Summary: Handle translated external Kudu tables
                 Key: IMPALA-9030
                 URL: https://issues.apache.org/jira/browse/IMPALA-9030
             Project: IMPALA
          Issue Type: Bug
            Reporter: Vihang Karajgaonkar
            Assignee: Vihang Karajgaonkar


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 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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)