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

   ## What is the purpose of the change
   
   This PR migrates ManuallyClosedSourceFunction in 
CoordinatorEventsToStreamOperatorRecipientExactlyOnceITCase from the deprecated 
legacy SourceFunction API to the modern FLIP-27 Source API
   
   
   ## Brief change log
   
     - Removed ManuallyClosedSourceFunction class that implemented the 
deprecated SourceFunction interface
     - Note: DataGeneratorSource cannot be used directly as this source emits 
no data and requires external control via static flags for test coordination
   
   
   ## Verifying this change
   
   Existing tests in 
CoordinatorEventsToStreamOperatorRecipientExactlyOnceITCase already cover this 
change:
   
    - testCheckpoint() - verifies operator coordinator events work correctly 
with aligned checkpoints
     - testUnalignedCheckpoint() - verifies operator coordinator events work 
correctly with unaligned checkpoints
     - testCheckpointWithSubtaskFailure() - verifies exactly-once semantics 
during subtask failures
     - testUnalignedCheckpointWithSubtaskFailure() - verifies exactly-once 
semantics during subtask failures with unaligned checkpoints
   
     All tests pass.
   
   ## 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): 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 
   


-- 
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