Steve Carlin created IMPALA-15134:
-------------------------------------
Summary: Calcite planner: Incorrect cardinality in Kudu explain
plan
Key: IMPALA-15134
URL: https://issues.apache.org/jira/browse/IMPALA-15134
Project: IMPALA
Issue Type: Bug
Reporter: Steve Carlin
For the following query in the runtime_filters.test in the functional_kudu db:
with t1 as (select month x, bigint_col y from alltypes limit 7301),
t2 as (select distinct int_col x, bigint_col y from alltypestiny limit 3)
select count(*) from t1, t2 where t1.x = t2.x
An incorrect cardinality is being calculated for the select node.
While I haven't researched this fully, it seems that there is a SELECT PlanNode
added for the Calcite planner that removes some IS NOT NULL data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
