[
https://issues.apache.org/jira/browse/SPARK-28155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889400#comment-16889400
]
Hyukjin Kwon commented on SPARK-28155:
--------------------------------------
[~Tonix517] said:
Hi Wenchen, do you think it is viable solution mentioned below?
Create a new V2WriteCommand case class and its Exec named maybe
OverwriteByQueryId to replace WriteToDataSourceV2, which accepts a QueryId so
that tests can pass.
Or should we keep WriteToDataSourceV2?
> Improve SQL optimizer's predicate pushdown performance for cascading joins
> --------------------------------------------------------------------------
>
> Key: SPARK-28155
> URL: https://issues.apache.org/jira/browse/SPARK-28155
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
