[IMPALA-2112] Support primary key/foreign key constraint as part of create table in Impala

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Impala 2.2
• Component/s: Catalog, Frontend
• Labels: planner
• Target Version: Product Backlog
• Assignee: Anurag Mantripragada
• Reporter: Marcel Kinard
• Created: 01/Jul/15 19:26
• Updated: 18/Feb/20 19:22
• Resolved: 18/Nov/19 19:51

Description

These would be advisory, ie, Impala would not attempt to enforce them. However, they could be used for cardinality estimation during query planning.

To be compatible with Hive:

• We neither enforce or validate integrity constraints. Hence, DISABLE and NOVALIDATE options are mandatory.
• RELY/NORELY is optional. The CBO is expected to use this information when a user specifies “RELY”. The default is NORELY.
• Since we do not yet have UNIQUE in Hive, the FK mentioned must be Primary Key column in parent table.

Support create table syntax like hive does:

• create table pk(id1 integer, id2 integer, primary key(id1, id2) DISABLE NOVALIDATE);
• create table fk(id1 integer, id2 integer, foreign key(id1, id2) references pk(id2, id1) DISABLE NOVALIDATE);
• create table T1(id integer, name string, primary key(id) DISABLE NOVALIDATE RELY