[ 
https://issues.apache.org/jira/browse/IMPALA-13544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mihaly Szjatinya resolved IMPALA-13544.
---------------------------------------
    Resolution: Fixed

> Expose TRANSLATED_TO_EXTERNAL property in SHOW CREATE TABLE
> -----------------------------------------------------------
>
>                 Key: IMPALA-13544
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13544
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>            Reporter: Gabor Kaszab
>            Assignee: Mihaly Szjatinya
>            Priority: Major
>              Labels: ramp-up
>
> When Impala creates a managed table (without the external keyword) HMS will 
> in fact create it as an external table anyway. When doing this under the hood 
> conversion HMS sets the TRANSLATED_TO_EXTERNAL table property to true so that 
> it can later on see if the table was explicitly created as external or not.
> There is some logic that depends on the value of this field. For instance 
> when renaming a table the folder of the could be also renamed based on how 
> this table property is set.
> When we issue a SHOW CREATE TABLE in impala this property is not visible in 
> the output, as a result the output is the same regardless of the table was 
> created as external or was converted to by HMS under the hood. Hive on the 
> other hand shows this property in the output of SHOW CREATE TABLE.
> My proposal is to add an improvement to Impala to show the 
> TRANSLATED_TO_EXTERNAL property in the SHOW CREATE TABLE output. Otherwise, 
> creating a table based on the SHOW CREATE TABLE output wouldn't be the same 
> table, for instance when being renamed it could have a different behaviour 
> when it comes to renaming the folder.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to