igalshilman opened a new pull request #7590: [FLINK-11329][core] Migrating 
CompositeSerializers
URL: https://github.com/apache/flink/pull/7590
 
 
   ## What is the purpose of the change
   
   This PR migrates the following serializers to the new 
`TypeSerializerSnapshot` abstraction:
   - ScalaOptionSerializer      4e1a755392
   - StreamElementSerializer 9a0ddc1c28
   - BufferEntrySerializer        9a56f43386
   - UnionSerializer                 317e6b863a
   - RowSerializer                    3a1a86799e
   - NullableSerializer             d93ff8a3a9
   - CompositeSerializer        ce253636d7
   
   ## Brief change log
   
   Each commit migrates a single serializer's `TypeSerializerConfigSnapshot` to 
the new `TypeSerializerSnapsoht`.
   
   ## Verifying this change
   
   Each migrated serializer has an associated `StateMigrationTest` that 
verifies snapshot backwards compatibility with previous versions.
   
   ## 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, 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 GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to