Skip to content

Avoid allowing payload class changes in HoodieStreamer #17442

@hudi-bot

Description

@hudi-bot

As part of [https://github.com//pull/13615/files#r2274346707] 

we came across a scenario, where HoodieStreamer allows switching payload classes. 

We don't allow this w/ spark data source writes. 

So, lets chase down why we allow this for HoodieStreamer and if no valid reasons are found, we should fix the gap and throw exception if a user tries to change the payload class w/ HoodieStreamer. 

 

JIRA info


Comments

22/Aug/25 16:48;linliu;Spark data source, actually allows payload classes overwritten.

Meanwhile, we know Hudi also allows merge strategy id, merge mode overwritten.

This is not a block for 1.1 release, since this behavior already exists.

I will do some scoping before start working on this.;;;

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:writerWrite client and core write operationsfrom-jirapriority:highSignificant impact; potential bugsstatus:pr-availablePull request availabletype:devtaskDevelopment tasks and maintenance work

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions