[IMPALA-5654] Disallow managed Kudu table to explicitly set Kudu tbl name in CREATE TABLE

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 2.8.0
• Fix Version/s: Impala 2.12.0
• Component/s: Frontend
• Labels: kudu
• Target Version: Product Backlog
• Epic Color: ghx-label-5
• Assignee: Gabor Kaszab
• Reporter: Matthew Jacobs
• Created: 12/Jul/17 18:25
• Updated: 22/Feb/19 22:33
• Resolved: 23/Jan/18 08:33

Description

There's no reason to allow this behavior. Managed tables create Kudu tables with the name (in Kudu) "impala::db_name.table_name". Renaming (in Impala) a managed Kudu table results in renaming the underlying Kudu table, e.g. rename table_name to new_table name results in changing the Kudu table to "impala::db_name.new_table_name". But allowing a new table to specify the kudu table name is inconsistent with the renaming behavior and just introduces opportunities for confusion.

  private void analyzeManagedKuduTableParams(Analyzer analyzer) throws AnalysisException {
    // If no Kudu table name is specified in tblproperties, generate one using the
    // current database as a prefix to avoid conflicts in Kudu.
    // TODO: Disallow setting this manually for managed tables
    if (!getTblProperties().containsKey(KuduTable.KEY_TABLE_NAME)) {
      getTblProperties().put(KuduTable.KEY_TABLE_NAME,
          KuduUtil.getDefaultCreateKuduTableName(getDb(), getTbl()));
    }

Issue Links

• is required by: IMPALA-6375 Allow setting 'kudu.table_name' and 'EXTERNAL' table properties in one step

Sub-Tasks

• Impala Doc: Disallow set kudu.table_name in CREATE and ALTER TABLE: Closed