[IMPALA-11809] Support non unique primary key for Kudu

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Impala 4.3.0
• Fix Version/s: Impala 4.3.0
• Component/s: Backend, Catalog, Frontend
• Epic Color: ghx-label-1
• Assignee: Wenzhe Zhou
• Reporter: Wenzhe Zhou
• Created: 20/Dec/22 21:30
• Updated: 02/May/23 16:11
• Resolved: 06/Feb/23 19:48

Description

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 partitions 3
STORED as KUDU;

CREATE TABLE tbl (i INT, s STRING, NON UNIQUE PRIMARY KEY)
PARTITION BY HASH 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;

Issue Links

• is related to: KUDU-1945 Support generation of surrogate primary keys (or tables with no PK)
• relates to: IMPALA-11906 Impala Doc: Support non unique primary key for Kudu table