gustavodemorais opened a new pull request, #29810: URL: https://github.com/apache/flink/pull/29810
## What is the purpose of the change PTFs with row semantics always receive retractions for upsert inputs because the planner requires UPDATE_BEFORE whenever there is no PARTITION BY. This adds an unnecessary ChangelogNormalize and hash exchange, e.g. for TO_CHANGELOG with an op_mapping without UPDATE_BEFORE. This PR keeps upsert mode for row semantics when the input has an upsert key and the PTF is insert-only or passes all columns through. ## Brief change log - Request upserts for row-semantic table arguments if the input has an upsert key and the PTF is insert-only or passes columns through, falling back to retract otherwise - Allow key-only deletes for row-semantic table arguments that consume upserts - Allow upsert output and pass-through columns with updates for row semantics, using the input upsert key as the output upsert key - Expose key-only deletes of inputs to PTF changelog queries - Update ArgumentTrait, ChangelogFunction and PTF docs ## Verifying this change - ProcessTableFunctionTest - ToChangelogTest - ProcessTableFunctionSemanticTests ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: yes - documented changelog behavior of SUPPORT_UPDATES and PASS_COLUMNS_THROUGH for row semantics - The serializers: no - The runtime per-record code paths (performance sensitive): no - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? (not applicable) --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes (please specify the tool below) 2.1.304 (Claude Code) with Opus 5.5 -- 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]
