Re: [I] Check the write operation configured by user for better troubleshooting [hudi]

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

nsivabalan commented on issue #15850:
URL: https://github.com/apache/hudi/issues/15850#issuecomment-4795489366

   Triage note: this issue appears to be resolved on current master.
   
   - The original error path (`HoodieAvroUtils.getNestedFieldVal` being called with an empty precombine field at `HoodieSparkSqlWriter.scala:305`) has been refactored into `HoodieCreateRecordUtils.scala`, where the call is now guarded by `if (shouldCombine && !orderingFields.isEmpty)` (around line 152). When no precombine/ordering field is set, `getNestedFieldVal` is no longer invoked, so the `(Part -) field not found in record` message can no longer surface from this path.
   - The underlying premise ("Hudi does not support upsert for table without preCombineKey") no longer holds. Per `HoodieTableConfig.inferMergingConfigsForPreV9Table` and HUDI-8413 (#12600), the default `RecordMergeMode` falls back to `COMMIT_TIME_ORDERING` when no ordering field is configured, which makes upsert on a table without a precombine field a supported flow.
   
   Reproducing the steps from the description on current master should succeed without the confusing exception. If anyone still hits a similar error in a recent release, please reopen with the version and a stack trace and we can take another look. Otherwise this can likely be closed.


-- 
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