You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Xianqing He (Jira)" <ji...@apache.org> on 2020/12/24 07:52:00 UTC
[jira] [Created] (IMPALA-10406) Query with analytic function
doesn't need to materialize the predicate pushed down to kudu
Xianqing He created IMPALA-10406:
------------------------------------
Summary: Query with analytic function doesn't need to materialize the predicate pushed down to kudu
Key: IMPALA-10406
URL: https://issues.apache.org/jira/browse/IMPALA-10406
Project: IMPALA
Issue Type: Improvement
Components: Frontend
Affects Versions: Impala 4.0
Reporter: Xianqing He
Assignee: Xianqing He
Fix For: Impala 4.0
The query with analytic function doesn't need to materialize the predicate pushed down to kudu.
E.g.
{code:java}
select min(n_nationkey) over(partition by n_regionkey) from tpch_kudu.nation t1 where t1.n_name in ('ALGERIA', 'ARGENTINA');
{code}
The plan
{code:java}
PLAN-ROOT SINK
|
02:ANALYTIC
| functions: min(n_nationkey)
| partition by: n_regionkey
| row-size=25B cardinality=2
|
01:SORT
| order by: n_regionkey ASC NULLS LAST
| row-size=23B cardinality=2
|
00:SCAN KUDU [tpch_kudu.nation t1]
kudu predicates: t1.n_name IN ('ALGERIA', 'ARGENTINA')
row-size=27B cardinality=2
{code}
We don't need to materialize the slot 'n_name'.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)