[IMPALA-12018] Consider runtime filters in resource estimates

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Impala 4.4.0
• Component/s: Frontend
• Target Version: Impala 4.4.0
• Epic Color: ghx-label-2
• Assignee: Riza Suminto
• Reporter: Csaba Ringhofer
• Created: 23/Mar/23 08:13
• Updated: 14/May/24 01:57
• Resolved: 20/Dec/23 03:08

Description

Currently Impala creates a plan first and looks for runtime filters bases on the complete plan.
IMPALA-3573 is about considering runtime filters during join ordering which would be a major change. Meanwhile it could be also useful to consider selective looking runtime filters in resource estimates without changing the plan topology.

Issue Links

• causes: IMPALA-12702 Est. #Rows in ExecSummary does not reflect reduction from runtime filter.
• is related to: IMPALA-13077 Equality predicate on partition column and uncorrelated subquery doesn't reduce the cardinality estimate
• is required by: IMPALA-12703 ExchangeNode should use getFilteredCardinality for costing.
• relates to: IMPALA-3573 Planner doesn't take into account runtime filter selectivity