[IMPALA-9971] Use defined table constraints during query planning

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Frontend
• Epic Color: ghx-label-12
• Assignee: Unassigned
• Reporter: Shant Hovsepian
• Created: 18/Jul/20 20:02
• Updated: 18/Jul/20 20:28

Description

With the implementation of IMPALA-3531 the planner now has access to defined table constraints. The Hive metastore supports defining nullability, uniquness, and referential integrity constraints. This metadata should be used for more effective query planning.

Issue Links

• depends upon: IMPALA-3531 Implement deferrable and optionally enforced PK/FK constraints

Sub-Tasks

• Use defined referential constraints for join cardinality calculations: Open
• Perform distinct elimination with constraint information: Open
• Join elimination based on referential integrity: Open
• Optimize logical view joins with table constraints: Open