[
https://issues.apache.org/jira/browse/IMPALA-12018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805752#comment-17805752
]
ASF subversion and git services commented on IMPALA-12018:
----------------------------------------------------------
Commit 117b35b17df9ff63301f19e3719d13ab777ccbeb in impala's branch
refs/heads/master from Riza Suminto
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=117b35b17 ]
IMPALA-12703: ExchangeNode should use getFilteredCardinality
IMPALA-12018 changed the CPU costing formula from using getCardinality()
to getFilteredCardinality() for DataStreamSink, HashJoinNode, JoinNode,
and NestedLoopJoinNode. However, it miss to do the same for
ExchangeNode, which is also eligible for cardinality reduction by
runtime filter. This patch fix the formula for ExchangeNode.
Testing
- Pass PlannerTest#testProcessingCost.
Change-Id: I62a649b67c75c46bd57d8ceda80265af3321d85b
Reviewed-on: http://gerrit.cloudera.org:8080/20880
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Consider runtime filters in resource estimates
> ----------------------------------------------
>
> Key: IMPALA-12018
> URL: https://issues.apache.org/jira/browse/IMPALA-12018
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Reporter: Csaba Ringhofer
> Assignee: Riza Suminto
> Priority: Major
> Fix For: Impala 4.4.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
