[
https://issues.apache.org/jira/browse/SPARK-34527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291876#comment-17291876
]
Apache Spark commented on SPARK-34527:
--------------------------------------
User 'karenfeng' has created a pull request for this issue:
https://github.com/apache/spark/pull/31666
> De-duplicated common columns cannot be resolved from USING/NATURAL JOIN
> -----------------------------------------------------------------------
>
> Key: SPARK-34527
> URL: https://issues.apache.org/jira/browse/SPARK-34527
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.0.0
> Reporter: Karen Feng
> Priority: Minor
>
> USING/NATURAL JOINS today have unexpectedly asymmetric behavior when
> resolving the duplicated common columns. For example, the left key columns
> can be resolved from a USING INNER JOIN, but the right key columns cannot.
> This is due to the Analyzer's
> [rewrite|https://github.com/apache/spark/blob/999d3b89b6df14a5ccb94ffc2ffadb82964e9f7d/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala#L3397]
> of NATURAL/USING JOINs, which uses Project to remove the duplicated common
> columns.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
