You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2022/10/12 19:26:00 UTC
[jira] [Commented] (SPARK-40773) Refactor checkCorrelationsInSubquery
[ https://issues.apache.org/jira/browse/SPARK-40773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616661#comment-17616661 ]
Apache Spark commented on SPARK-40773:
--------------------------------------
User 'allisonwang-db' has created a pull request for this issue:
https://github.com/apache/spark/pull/38226
> Refactor checkCorrelationsInSubquery
> ------------------------------------
>
> Key: SPARK-40773
> URL: https://issues.apache.org/jira/browse/SPARK-40773
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.4.0
> Reporter: Allison Wang
> Priority: Major
>
> Currently, the logic in `checkCorrelationsInSubquery` is inefficient and difficult to understand. It uses `foreachUp` to traverse the subquery plan tree, and traverses down an entire subtree of a plan node to check whether it contains any outer references. We can use recursion instead to traverse the plan tree only once.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org