You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Sahil Takiar (JIRA)" <ji...@apache.org> on 2019/04/05 15:45:00 UTC
[jira] [Created] (IMPALA-8391) Impala Doc
Sahil Takiar created IMPALA-8391:
------------------------------------
Summary: Impala Doc
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
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)