You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2025/11/29 21:03:00 UTC
[jira] [Assigned] (SPARK-54525) Disable nested struct coercion in MERGE INTO
[ https://issues.apache.org/jira/browse/SPARK-54525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun reassigned SPARK-54525:
-------------------------------------
Assignee: Szehon Ho
> Disable nested struct coercion in MERGE INTO
> --------------------------------------------
>
> Key: SPARK-54525
> URL: https://issues.apache.org/jira/browse/SPARK-54525
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 4.1.0
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Priority: Major
> Labels: pull-request-available
>
> https://issues.apache.org/jira/browse/SPARK-53482 allow MERGE INTO to support case where assignment value is a struct with less fields than the assignment key, ie UPDATE SET big_struct = source.small_struct
> This bring some interesting question, for example there is some ambiguity in user intent. Does the UPDATE SET * mean set all nested fields or top level columns. In the first case, missing fields are kept. In the second case, missing fields are nullified.
> https://issues.apache.org/jira/browse/SPARK-54289 is a bit controversial, choosing one interpretation over another. A SQLConf may not be the right choice, and instead we may need to introduce some new syntax, which require more discussion. So disabling for 4.1.
--
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