[GitHub] igalshilman opened a new pull request #7658: [FLINK-10493][core] Migrating the TupleSerializerBase serializers family

[GitBox <gi...@apache.org>]

igalshilman opened a new pull request #7658: [FLINK-10493][core] Migrating the TupleSerializerBase serializers family
URL: https://github.com/apache/flink/pull/7658
 
 
   ## What is the purpose of the change
   
   This PR migrates the serializers that inherit from the `TupleSerializerBase` to the new type serializer snapshot abstraction.
   The following serializers are migrated as part of this PR:
   - `TupleSerializer`
   - `Tuple0Serializer`
   - `Tuple2CaseClassSerializer`
   - `CaseClassSerializer` (scala macro generated)
   
   ## Brief change log
   
   - b4b34adbcf Make case class definition top level in tests to avoid instance classes .
   - 1db6088f24 Migrate the Tuple0Serializer
   - 36b97c5f28 Add new TupleSerializerSnapshot
   - 6f52deef7b Add Tuple2 snapshot class
   - 779f93ce0b Add SpecificCaseClassSerializer
   - af53660a73 Migrate the CaseClassSerializer with the tuple serializer
   
   ## Verifying this change
   
   This PR adds serializer migration tests.
   
   ## 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:
users@infra.apache.org


With regards,
Apache Git Services