You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/07/20 07:36:00 UTC
[jira] [Commented] (SPARK-27815) Improve SQL optimizer's predicate
pushdown performance for cascading joins
[ https://issues.apache.org/jira/browse/SPARK-27815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889402#comment-16889402 ]
Hyukjin Kwon commented on SPARK-27815:
--------------------------------------
There was a mistake about JIRA ID and commit. The JIRA is now switched to SPARK-28155
> Improve SQL optimizer's predicate pushdown performance for cascading joins
> ---------------------------------------------------------------------------
>
> Key: SPARK-27815
> URL: https://issues.apache.org/jira/browse/SPARK-27815
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Yesheng Ma
> Assignee: Yesheng Ma
> Priority: Major
> Fix For: 3.0.0
>
>
> The current catalyst optimizer's predicate pushdown is divided into two separate rules: PushDownPredicate and PushThroughJoin. This is not efficient for optimizing cascading joins such as TPC-DS q64, where a whole default batch is re-executed just due to this. We need a more efficient approach to pushdown predicate as much as possible in a single pass.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org