szehon-ho opened a new pull request, #53490: URL: https://github.com/apache/spark/pull/53490
### What changes were proposed in this pull request? Completely disable "spark.sql.mergeNestedTypeCoercion.enabled" conf for Spark 4.1 ### Why are the changes needed? As https://github.com/apache/spark/pull/53326 is not allowed for Spark 4.1 , we should disable the feature completely then. It doesn't make sense to allow the user to opt-in the feature, when we plan to completely change the meaning for subsequent releases. Background, without this, there is a risk of data loss, because values for nested field that do not exist in source are all nullified in MERGE INTO with UPDATE SET * ### Does this PR introduce _any_ user-facing change? No, unreleased ### How was this patch tested? Unit test ### Was this patch authored or co-authored using generative AI tooling? No -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
