gaoyunhaii opened a new pull request #14820:
URL: https://github.com/apache/flink/pull/14820


   ## What is the purpose of the change
   
   This PR enables triggering checkpoint barrier handle for non-source tasks. 
   
   To support checkpoints after some tasks finished, non-source tasks might 
also receive RPC trigger of checkpoint after all their precedent tasks get 
finished. In this case, it need to trigger checkpoint barrier handler to insert 
barriers. This PR provides the functionality to notify checkpoint barrier on 
RPC trigger
   
   ## Brief change log
   
   *(for example:)*
     - a3daa2b88a7c1609daf2bb55742971eabe5dacf0 refactors the current 
implementation to expose CheckpointBarrierHandler.
     - b4baae6e24556aec841fb1c4fcedfec234e3c0cd notifies the non-source stream 
tasks' checkpoint barrier handler on RPC trigger.
     - 326d8751ac2aac4255b5e94da8e8f46a424c55c5 fixes the tests that using 
non-source task that directly perform checkpoint on trigger.
   
   
   ## Verifying this change
   
   Added UT to verify that checkpoint barrier handler get triggered on RPC 
checkpoint trigger.
   
   ## 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/Mesos, 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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to