[
https://issues.apache.org/jira/browse/IMPALA-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rodoni closed IMPALA-8391.
-------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.3.0
> Impala Doc: ALTER TABLE RENAME on managed Kudu table renames underlying Kudu
> table
> ----------------------------------------------------------------------------------
>
> Key: IMPALA-8391
> URL: https://issues.apache.org/jira/browse/IMPALA-8391
> Project: IMPALA
> Issue Type: Sub-task
> Components: Docs
> Reporter: Sahil Takiar
> Assignee: Alex Rodoni
> Priority: Major
> Labels: future_release_doc, in_33
> Fix For: Impala 3.3.0
>
>
> The Impala-Kudu docs:
> [http://impala.apache.org/docs/build/html/topics/impala_kudu.html]
> [http://impala.apache.org/docs/build/html/topics/impala_tables.html]
> Need to be updated after IMPALA-7640 is merged.
> Specifically this part of the docs will no longer be accurate:
> {quote}
> When you create a Kudu table through Impala, it is assigned an internal Kudu
> table name of the form {{impala::db_name.table_name}}. You can see the
> Kudu-assigned name in the output of {{DESCRIBE FORMATTED}}, in the
> {{kudu.table_name}} field of the table properties. The Kudu-assigned name
> remains the same even if you use {{ALTER TABLE}} to rename the Impala table
> or move it to a different Impala database. You can issue the statement{{ALTER
> TABLE impala_name SET TBLPROPERTIES('kudu.table_name' =
> 'different_kudu_table_name')}} for the external tables created with the
> {{CREATE EXTERNAL TABLE}} statement. Changing the {{kudu.table_name}}property
> of an external table switches which underlying Kudu table the Impala table
> refers to. The underlying Kudu table must already exist.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
