SteNicholas opened a new pull request #13813:
URL: https://github.com/apache/flink/pull/13813


   ## What is the purpose of the change
   
   *Currently Flink can only handle schemas up to a size of 65535 bytes, and 
`AvroSerializerSnapshot` cannot handle large schema. If size of schame exceed 
65535 bytes, the `UTFDataFormatException` could be thrown. 
`AvroSerializerSnapshot` should introduce a V3 that uses 
`StringValue.writeString()` and `StringValue.readString()` to handle the string 
encoding.*
   
   ## Brief change log
   
     - *`AvroSerializerSnapshot` introduces a V3 that uses 
`StringValue.writeString()` in `writeSnapshot()` and `StringValue.readString()` 
in `readSnapshot()`.*
   
   ## Verifying this change
   
     - *`AvroSerializerSnapshotTest` adds the test method 
`largeSchemaWithExceedV2ThresholdSizeShouldResultInCompatibleV3Serializer` to 
verify the test case whether the large schema which exceeds a threshold size of 
65535 bytes is compatible with the new version 3 of `AvroSerializerSnapshot`.*
   
   ## 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