Steve Carlin created IMPALA-15613:
-------------------------------------
Summary: Kudu planner returns bad cardinality estimate
Key: IMPALA-15613
URL: https://issues.apache.org/jira/browse/IMPALA-15613
Project: IMPALA
Issue Type: Bug
Reporter: Steve Carlin
Not sure we can do anything about this one, but it should at least be
examined...
One of our queries in runtime_filters.test has a bad cardinality estimate for
kudu
{code:java}
Query: explain select * from functional_kudu.alltypes where
greatest(functional_kudu.alltypes.month, 1000) IS NOT NULL
+-----------------------------------------------------------------------------+
| Explain String |
+-----------------------------------------------------------------------------+
| Max Per-Host Resource Reservation: Memory=4.00MB Threads=3 |
| Per-Host Resource Estimates: Memory=14MB |
| Codegen disabled by planner |
| |
| PLAN-ROOT SINK |
| | |
| 01:EXCHANGE [UNPARTITIONED] |
| | |
| 00:SCAN KUDU [functional_kudu.alltypes] |
| predicates: greatest(functional_kudu.alltypes.`month`, 1000) IS NOT NULL |
| row-size=97B cardinality=730 |
+-----------------------------------------------------------------------------+
{code}
{code:java}
{code}
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
