Fix concurrent schema evolution conflict bug

Open hudi-bot opened this issue 2 months ago • 2 comments

For schema conflict resolution, previously we assume all instances with type COMMIT or DELTA_COMMIT comes with a valid schema. This is not true as there can be cases where hoodie streamer makes empty insert commits just for purpose of saving some commit metadata like the checkpoint offset while no data is written to the hudi table (maybe all messages fetched from a data source like kafka turns out to be not useful in that batch). In such a case, the commit metadata does not necessarily comes with a valid table schema ("schema" field is ""null"")

The change accommodates for this corner case.

JIRA info

Link: https://issues.apache.org/jira/browse/HUDI-8491
Type: Bug
Fix version(s):
- 1.1.0

Nov 30 '25 11:11 hudi-bot

Linked PR(s)

https://github.com/apache/hudi/pull/12221

Dec 09 '25 04:12 hudi-bot

@Davis-Zhang-Onehouse is this still an issue? I remember it is fixed (by another PR?), but the related PR is closed.

Dec 12 '25 00:12 yihua