You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Feng Zhu (Jira)" <ji...@apache.org> on 2022/01/19 10:24:00 UTC
[jira] [Commented] (SPARK-37932) Analyzer can fail when join left side and right side are the same view
[ https://issues.apache.org/jira/browse/SPARK-37932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478537#comment-17478537 ]
Feng Zhu commented on SPARK-37932:
----------------------------------
{code:scala}
{code}
> 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
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org