irodriguezclaveria opened a new issue, #8498: URL: https://github.com/apache/paimon/issues/8498
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Motivation Flink FLIP-510 (Drop ChangelogNormalize for operations which don't need it) allows a sink to advertise a "keyOnlyDeletes" capability, so the Flink planner can drop the upstream ChangelogNormalize node when the source produces deletes by key. This is especially useful for CDC sources, where the UPDATE_AFTER already carries the full row: dropping ChangelogNormalize removes its state and overhead with no loss of correctness. ### Solution Advertise the FLIP-510 keyOnlyDeletes capability on Paimon primary-key table sinks. - Gated behind a new table option `sink.key-only-deletes.enabled` (default `false`), so existing plans are unchanged unless explicitly opted in. - The API only exists in Flink 2.1+, so the behavior is wired through `ChangelogModeUtils` in `paimon-flink1-common` (no-op) and `paimon-flink2-common` (sets the flag), keeping `paimon-flink-common` compiling against both Flink 1.x and 2.x. Tested in a real environment: ChangelogNormalize is correctly dropped. ### Anything else? _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
