[jira] [Commented] (IMPALA-11254) Create Kudu table with hash + range partitions fails

["Quanlong Huang (Jira)" <ji...@apache.org>]

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

Quanlong Huang commented on IMPALA-11254:
-----------------------------------------

I think it's by design. Kudu rows are first partitioned and then grouped in ranges. In our doc, we also mention hash clause should be put before the range clause:
{code}kudu_partition_clause ::= [ hash_clause [, ...]] [, range_clause ]{code}
https://impala.apache.org/docs/build/html/topics/impala_create_table.html

> Create Kudu table with hash + range partitions fails
> ----------------------------------------------------
>
>                 Key: IMPALA-11254
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11254
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.0.0
>            Reporter: Manish Maheshwari
>            Priority: Critical
>
> The below query fails -
> {code:java}
> CREATE TABLE lsr (
> end_time TIMESTAMP,
> uuid String,
> start_m_tmsi bigint,
> start_time TIMESTAMP,
> duration TIMESTAMP,
> partition_date date,
> PRIMARY KEY(end_time, uuid) 
> ) 
> PARTITION BY RANGE (end_time)
> (
> PARTITION VALUES < '2011-09-01',
> PARTITION '2011-09-01' <= VALUES < '2011-10-01',
> PARTITION '2011-10-01' <= VALUES < '2011-11-01',
> PARTITION '2011-11-01' <= VALUES
> ), 
> HASH (uuid) PARTITIONS 5
> STORED AS KUDU ;
>  {code}
> If you swap the order of range and hash partitions, it works.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org