You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/03/18 20:37:00 UTC

[jira] [Updated] (SPARK-56054) Fix aliased nested fields ignored for schema evolution in MERGE

     [ https://issues.apache.org/jira/browse/SPARK-56054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated SPARK-56054:
-----------------------------------
    Labels: pull-request-available  (was: )

> Fix aliased nested fields ignored for schema evolution in MERGE
> ---------------------------------------------------------------
>
>                 Key: SPARK-56054
>                 URL: https://issues.apache.org/jira/browse/SPARK-56054
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 4.2.0
>            Reporter: Johan Lasperas
>            Priority: Minor
>              Labels: pull-request-available
>
> Small bug in the [initial implementation of schema evolution in MERGE](https://github.com/apache/spark/pull/51698): when a struct in the source is used aliased in a direct assignment clause in MERGE, it's fields aren't considered for schema evolution.
> Example:
> ```
> source.mergeInto("target", condition)
>   .whenMatched()
>   update(Map("info" -> col("source.info").as("info")))
>   .withSchemaEvolution()
>   .merge()
> ```
> where `info` is a struct that contains an extra field in the source compared to the target. The extra field is ignored during schema evolution and isn't added to the target table.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org