[
https://issues.apache.org/jira/browse/SPARK-37932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-37932.
---------------------------------
Fix Version/s: 3.3.0
3.2.2
Resolution: Fixed
Issue resolved by pull request 35684
[https://github.com/apache/spark/pull/35684]
> Analyzer can fail when join left side and right side are the same view
> ----------------------------------------------------------------------
>
> Key: SPARK-37932
> URL: https://issues.apache.org/jira/browse/SPARK-37932
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.2.0
> Reporter: Feng Zhu
> Priority: Major
> Fix For: 3.3.0, 3.2.2
>
> Attachments: sql_and_exception
>
>
> See the attachment for details, including SQL and the exception information.
> * sql1, there is a normal filter (LO_SUPPKEY > 10) in the right side
> subquery, Analyzer works as expected;
> * sql2, there is a HAVING filter(HAVING COUNT(DISTINCT LO_SUPPKEY) > 1) in
> the right side subquery, Analyzer failed with "Resolved attribute(s)
> LO_SUPPKEY#337 missing ...".
> From the debug info, the problem seems to be occurred after the rule
> DeduplicateRelations is applied.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
