cshuo opened a new pull request, #18694:
URL: https://github.com/apache/hudi/pull/18694
### Describe the issue this Pull Request addresses
Flink source v2 should not emit delete records for batch snapshot reads. For
MOR tables, source v2 was enabling delete emission based only on table type,
which caused batch queries to return deleted records as rows with null payload
fields instead of preserving snapshot read semantics.
This PR aligns source v2 delete emission with streaming mode and adds
regression coverage for batch reads.
### Summary and Changelog
- Updated `HoodieTableSource` to enable `emitDelete` only for MOR reads
running in streaming mode.
- Added `ITTestHoodieDataSource.testIgnoreEmitDeleteForBatchReading` to
verify batch reads do not emit delete records with source v2 enabled or
disabled.
### Impact
- Fixes Flink source v2 batch snapshot reads so deleted MOR records are
filtered out instead of emitted as delete rows.
### Risk Level
low
<!-- Accepted values: none, low, medium or high. Other than `none`, explain
the risk.
If medium or high, explain what verification was done to mitigate the
risks. -->
### Documentation Update
<!-- Describe any necessary documentation update if there is any new
feature, config, or user-facing change. If not, put "none".
- The config description must be updated if new configs are added or the
default value of the configs are changed.
- Any new feature or user-facing change requires updating the Hudi website.
Please follow the
[instruction](https://hudi.apache.org/contribute/developer-setup#website)
to make changes to the website. -->
### Contributor's checklist
- [ ] Read through [contributor's
guide](https://hudi.apache.org/contribute/how-to-contribute)
- [ ] Enough context is provided in the sections above
- [ ] Adequate tests were added if applicable
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
