[jira] [Commented] (KUDU-1665) KUDU lets you create table with wrong/non existent 'kudu.key_columns' columns and then it fails to load/drop the table

["Pavan Kulkarni (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533947#comment-15533947 ] 

Pavan Kulkarni commented on KUDU-1665:
--------------------------------------

Sorry for the unrelated comment to the above issue, but I observed that though it's mentioned that SPLIT ROWS is optional with DISTRIBUTE BY RANGE, it throws exception when not provided. Not sure if it's a bug or documentation needs to be updated. Let me know If I have to create a ticket for the same.

> KUDU lets you create table with wrong/non existent 'kudu.key_columns' columns and then it fails to load/drop the table
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: KUDU-1665
>                 URL: https://issues.apache.org/jira/browse/KUDU-1665
>             Project: Kudu
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.10.0
>         Environment: Linux 
>            Reporter: Pavan Kulkarni
>              Labels: kudu
>
> Create a table
> CREATE TABLE test(
>   id INT,
>   display_name STRING
> )
> DISTRIBUTE BY RANGE (id)
> SPLIT ROWS ((10000),(20000),(30000))
> TBLPROPERTIES(
> 'storage_handler' = 'com.cloudera.kudu.hive.KuduStorageHandler',
> 'kudu.table_name' = 'test',
> 'kudu.master_addresses' = 'master_server:port',
> 'kudu.key_columns' = 'id,wrong_column,non_existent_column'
> );
> It succesfully creates the table, but on loading or dropping the table you get an exception as follows:
> ERROR: AnalysisException: Some key columns were not found in the set of columns. List of column names: [wrong_column,non_existent_column]
> CAUSED BY: TableLoadingException: Some key columns were not found in the set of columns. List of column names: [wrong_column,non_existent_column]
> The fix should be to check the id columns exist as legit columns in the table before creating it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)