rionmonster opened a new pull request, #29842:
URL: https://github.com/apache/flink/pull/29842

   ## What is the purpose of the change
   
   Backport of #29583 to release-2.3.
   
   ## Brief change log
   
   Cherry-pick of ac930c9793c. Only tests needed changes:
   - FLINK-41282 isn't on this branch: its restore program and test cases are 
left out, and the `UserRegionsPK` table that the new input-0 test uses is 
created in the test setup, as FLINK-41282 does.
   - `MultiJoinTest.xml` is regenerated on this branch; the plans change in the 
same 25 cases as on master.
   - The restore program `three-way-join-upsert-inputs-with-restore` is 
regenerated on this branch, which can't load the Flink 2.5 plan.
   - Without FLINK-40528, the sink's deletes carry the full row, so the 
expected `-D` rows of that restore program have all fields.
   
   ## Verifying this change
   
   The tests of #29583, run on this branch. With the upsert handling disabled, 
the same tests fail as on master: 10 of the upsert operator tests, 
`MultiJoinSemanticTests` and the restore test.
   
   ## 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)`: no
   - The serializers: no
   - The runtime per-record code paths (performance sensitive): yes, as in 
#29583
   - 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
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [x] Yes (please specify the tool below)
   
   Generated-by: Claude Code (Claude 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]

Reply via email to