[
https://issues.apache.org/jira/browse/SPARK-39144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-39144.
---------------------------------
Fix Version/s: 3.3.0
Resolution: Fixed
Issue resolved by pull request 36503
[https://github.com/apache/spark/pull/36503]
> Nested subquery expressions deduplicate relations should be done bottom up
> --------------------------------------------------------------------------
>
> Key: SPARK-39144
> URL: https://issues.apache.org/jira/browse/SPARK-39144
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.3.0
> Reporter: Rui Wang
> Assignee: Rui Wang
> Priority: Major
> Fix For: 3.3.0
>
>
> When we have nested subquery expressions, there is a chance that deduplicate
> relations could replace an attributes with a wrong one. This is because the
> attributes replacement is done by top down than bottom up. This could happen
> if the subplan gets deduplicate relations first (thus two same relation with
> different attributes id), then a more complex plan built on top of the
> subplan (e.g. a UNION of queries with nested subquery expressions) can
> trigger this wrong attribute replacement error.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
