Re: [I] [SUPPORT] After upgrading hudi 0.14.1, use Spark SQL merge into to update the matched_action, the case of the column name and the expression name does not match, resulting in an exception. [hudi]

["deepakpanda93 (via GitHub)" <gi...@apache.org>]

deepakpanda93 commented on issue #10558:
URL: https://github.com/apache/hudi/issues/10558#issuecomment-4851125222

   Hello @KnightChess , The MERGE INTO command has been substantially reworked since 0.14.1. Column resolution in MergeIntoHoodieTableCommand now matches SET-clause attributes to target columns via Spark's case-insensitive resolver (spark.sql.caseSensitive defaults to false), so ... WHEN MATCHED THEN UPDATE SET ID=source.ID against a column named id should resolve correctly. The pkless MERGE INTO code that introduced this regression ([#9083](https://github.com/apache/hudi/pull/9083)) has been reworked (including the Spark-4 analysis restructuring in [#12772](https://github.com/apache/hudi/pull/12772)).
   
   Note: the originally-proposed fix ([#10826](https://github.com/apache/hudi/pull/10826)) was closed without merging, and it's the resolver rework — not that PR — that addresses this.
   
   Could you retest your exact repro on a recent 1.1.x release? If it works (as the current resolution path suggests), we'll close this out; if it still fails with the case mismatch, please share the stack and we'll add a targeted fix + test. Thanks!


-- 
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: commits-unsubscribe@hudi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org