Riza Suminto created IMPALA-12703:
-------------------------------------

             Summary: ExchangeNode should use getFilteredCardinality for 
costing.
                 Key: IMPALA-12703
                 URL: https://issues.apache.org/jira/browse/IMPALA-12703
             Project: IMPALA
          Issue Type: Bug
          Components: Frontend
            Reporter: Riza Suminto
            Assignee: Riza Suminto


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.

[https://github.com/apache/impala/blob/cdac777c51febc99500b8426c2b3aabc7e9addd7/fe/src/main/java/org/apache/impala/planner/ExchangeNode.java#L236-L237]
 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to