Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-7640 ALTER TABLE RENAME on managed Kudu table should rename underlying Kudu table
  3. IMPALA-8391

Impala Doc: ALTER TABLE RENAME on managed Kudu table renames underlying Kudu table

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • Impala 3.3.0
    • Docs
    • ghx-label-4

    Description

      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:

      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.

      Attachments

        Activity

          People

            arodoni Alexandra Rodoni
            stakiar Sahil Takiar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: