[
https://issues.apache.org/jira/browse/SPARK-34741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-34741.
---------------------------------
Fix Version/s: 3.2.0
Resolution: Fixed
Issue resolved by pull request 31835
[https://github.com/apache/spark/pull/31835]
> MergeIntoTable should avoid ambiguous reference
> -----------------------------------------------
>
> Key: SPARK-34741
> URL: https://issues.apache.org/jira/browse/SPARK-34741
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.1.1
> Reporter: wuyi
> Assignee: wuyi
> Priority: Major
> Fix For: 3.2.0
>
>
> When resolving the {{UpdateAction}}, which could reference attributes from
> both target and source tables, Spark should know clearly where the attribute
> comes from when there're conflicting attributes instead of picking up a
> random one.
--
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
