[
https://issues.apache.org/jira/browse/SPARK-54525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Szehon Ho updated SPARK-54525:
------------------------------
Description:
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.
was:
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 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.
> 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
> Priority: Major
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
