[
https://issues.apache.org/jira/browse/KUDU-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898008#comment-15898008
]
Todd Lipcon commented on KUDU-1665:
-----------------------------------
Hi [[email protected]]. Is this still an issue with the latest release of
Impala? The behavior of primary keys and partitioning clauses has been much
improved since you first reported this. If so, please follow up by reporting a
JIRA on the Impala issue tracker.
> 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: 1.0.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.15#6346)
