cloud-fan commented on PR #44159:
URL: https://github.com/apache/spark/pull/44159#issuecomment-1838845564
After a second though, this means we can always do UPDATE/INSERT * with
completely different column set in target and source tables, such as `a, b, c`
in target and `x, y, z` in source.
cloud-fan closed pull request #44159: [SPARK-46244][SQL] INSERT/UPDATE * in
MERGE should follow the same semantic of INSERT BY NAME
URL: https://github.com/apache/spark/pull/44159
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
cloud-fan commented on PR #44159:
URL: https://github.com/apache/spark/pull/44159#issuecomment-1838428215
cc @viirya @gengliangwang
--
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 c
cloud-fan opened a new pull request, #44159:
URL: https://github.com/apache/spark/pull/44159
### What changes were proposed in this pull request?
This is to fix the MERGE INSERT/UPDATE * behavior to make it easier to use,
and also to make it consistent with the INSERT BY NAME
