[HIVE-17039] Implement optimization rewritings that rely on database SQL constraints

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Done
• Affects Version/s: 3.0.0
• Component/s: Logical Optimizer
• Assignee: Unassigned Assign to me
• Reporter: Jesús Camacho Rodríguez
• Created: 05/Jul/17 12:47
• Updated: 27/Feb/24 22:24
• Resolved: 15/Sep/19 19:10

Description

Hive already has support to declare multiple SQL constraints (PRIMARY KEY, FOREIGN KEY, UNIQUE, and NOT NULL). Although these constraints cannot be currently enforced on the data, they can be made available to the optimizer by using the 'RELY' keyword.

This ticket is an umbrella for all the rewriting optimizations based on SQL constraints that we will be including in Hive.

Issue Links

• is blocked by: HIVE-17054 Expose SQL database constraints to Calcite

Sub-Tasks

• Join elimination in the presence of FK relationship: Closed
• Aggregate elimination with UNIQUE and NOT NULL column: Resolved
• Expose NOT NULL constraint in optimizer so constant folding can take advantage of it: Resolved
• Remove non unique columns from group by keys if not referenced later: Closed
• Transform LEFT/RIGHT OUTER into INNER join in the presence of FK relationship: Closed