godfreyhe opened a new pull request #15164:
URL: https://github.com/apache/flink/pull/15164


   
   
   ## What is the purpose of the change
   
   *This pr aims to introduce StateDeclaration which could let the planner know 
the state description for an operator, and support json 
serialization/deserialization for the states in StreamExecGroupAggregate*
   
   
   ## Brief change log
   
     - *Support StreamExecMiniBatchAssigner json serialization/deserialization*
     - *Introduce StateDeclaration which could let the planner know the state 
description for an operator*
     - *Support json serialization/deserialization for the states in 
StreamExecGroupAggregate*
     -  *Add test for state evolution in an ExecNode*
   
   
   ## Verifying this change
   
   
   This change added tests and can be verified as follows:
   
     - *Extended GroupAggregateJsonPlanTest which could verify the state 
structure used in StreamExecGroupAggregate*
     - *Added DistinctJsonPlanTest and MultipleVersionOperatorITCase to verify 
the state evolution for an operator in a test ExecNode*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / 
don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (not applicable / docs / JavaDocs 
/ **not documented**)
   


----------------------------------------------------------------
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:
[email protected]


Reply via email to