Myasuka opened a new pull request #7598: [FLINK-11333][protobuf] First-class serializer support for Protobuf types URL: https://github.com/apache/flink/pull/7598 ## What is the purpose of the change Support Protobuf types directly in Flink. Unlike the built-in avro serializer of Flink, check whether schema evolvable left to Protobuf itself not checking before any code running currently. This is a known limitation and recorded in [FLINK-11333's comments](https://issues.apache.org/jira/browse/FLINK-11333?focusedCommentId=16755185&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16755185). ## Brief change log - Support to extract `ProtobufTypeInfo` within `TypeExtractor`. - Support to (de)serialize protobuf's message directly without introducing `chill-protobuf` and Kryo. - Support to migrate old savepoint data which serialized by kryo serializer to use current newly `ProtobufSeriazlier` - Also support to build protoc on travis. ## Verifying this change This change added tests and can be verified as follows: - Added unit tests for `ProtobufTypeInfo`, `ProtobufSeriazlier` and `ProtobufSeriazlierSnapshot`. - Extended integration test to verify whether could migrate old savepoint data with kryo serializer to use current newly `ProtobufSeriazlier`. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): yes - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: yes - The runtime per-record code paths (performance sensitive): no, should not. - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: yes, savepoint data might need to be migarated. - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? yes - If yes, how is the feature documented? docs
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
