You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Aman Sinha (Jira)" <ji...@apache.org> on 2020/04/10 15:13:00 UTC
[jira] [Resolved] (IMPALA-9183) TPC-DS query 13 - customer_address
predicates not propagated to scan
[ https://issues.apache.org/jira/browse/IMPALA-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aman Sinha resolved IMPALA-9183.
--------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> TPC-DS query 13 - customer_address predicates not propagated to scan
> --------------------------------------------------------------------
>
> Key: IMPALA-9183
> URL: https://issues.apache.org/jira/browse/IMPALA-9183
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 3.4.0
> Reporter: David Rorke
> Assignee: Aman Sinha
> Priority: Major
> Labels: tpc-ds
> Fix For: Impala 4.0
>
> Attachments: profile_q13.txt, profile_q13_mod.txt, q13_mod_plan.png, q13_plan.png, query13.sql, query13_mod.sql
>
>
> TPC-DS query 13 has a set of predicates on the customer_address table, ca_state column that are currently evaluated after the join of customer_address and store_sales. The ca_state predicates could be pushed down to the customer_address scan node. This would reduce the size of the join input by a factor of 3.4.
> As an experiment I added an additional redundant predicate to the query (see attached query13_mod.sql) which causes the planner to evaluate the predicate at the scan node.
> Performance of the original and modified queries at 10 TB scale factor:
> Original: 164 seconds
> Modified: 44 seconds
> Query profiles for both versions attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org