You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Wenzhe Zhou (Jira)" <ji...@apache.org> on 2023/02/06 19:49:00 UTC
[jira] [Resolved] (IMPALA-11809) Support non unique primary key for Kudu
[ https://issues.apache.org/jira/browse/IMPALA-11809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenzhe Zhou resolved IMPALA-11809.
----------------------------------
Fix Version/s: Impala 4.3.0
Resolution: Fixed
> Support non unique primary key for Kudu
> ---------------------------------------
>
> Key: IMPALA-11809
> URL: https://issues.apache.org/jira/browse/IMPALA-11809
> Project: IMPALA
> Issue Type: New Feature
> Components: Backend, Catalog, Frontend
> Affects Versions: Impala 4.3.0
> Reporter: Wenzhe Zhou
> Assignee: Wenzhe Zhou
> Priority: Major
> Fix For: Impala 4.3.0
>
>
> Kudu engine adds support for non unique primary key. It adds a column 'auto_increment_id' automatically in a table which has non unique primary key. The non unique primary key and 'auto_increment_id' form unique composite primary key for the table.
> Impala need to add syntactic support for creating Kudu table with non unique primary key like:
> CREATE TABLE tbl (i INT NON UNIQUE PRIMARY KEY, s STRING)
> PARTITION BY HASH (i) partitions 3
> STORED as KUDU;
>
> CREATE TABLE tbl (i INT, s STRING, NON UNIQUE PRIMARY KEY(i))
> PARTITION BY HASH (i) partitions 3
> STORED as KUDU;
>
> CREATE TABLE tbl NON UNIQUE PRIMARY KEY(id)
> PARTITION BY HASH (id) partitions 3
> STORED as KUDU
> AS SELECT id, string_col FROM functional.alltypes WHERE id = 10;
--
This message was sent by Atlassian Jira
(v8.20.10#820010)