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

   ## What is the purpose of the change
   
    As part of the async execution model of disaggregated state management, 
this PR gives the basic definition of `StreamingOperator` integrated with async 
execution.
   
   The philosophy behind this PR is **we are trying NOT to invade the previous 
code path**. The most strict thing is that **it MUST NOT affect any _hot path_ 
without this feature**.
   
   By the way, the type parameter of record around `AsyncExecutionController` 
is erased, since the stream operator does not have the knowledge of record 
type, and the `AEC` does not need it.
   
   ## Brief change log
   
    - Erase the type parameter of record around `AsyncExecutionController` 
    - Define the `AbstractAsyncStateStreamOperator` and 
`AbstractAsyncStateStreamOperatorV2` corresponding to the 
`AbstracStreamOperator` and `AbstracStreamOperatorV2` respectively.
    - Wire the record processing logic with new introduced abstract stream 
operators in `RecordProcessorUtils`.
    
   
   ## Verifying this change
   
   This change around `AEC` is already covered by existing tests. Basic UTs for 
new operators are added.
   
   ## 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
     - 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