You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/01/20 08:59:00 UTC

[jira] [Updated] (FLINK-11333) First-class support for Protobuf types with evolvable schema

     [ https://issues.apache.org/jira/browse/FLINK-11333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Ewen updated FLINK-11333:
---------------------------------
    Labels: pull-request-available usability  (was: pull-request-available)

> First-class support for Protobuf types with evolvable schema
> ------------------------------------------------------------
>
>                 Key: FLINK-11333
>                 URL: https://issues.apache.org/jira/browse/FLINK-11333
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / Type Serialization System
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Yun Tang
>            Priority: Major
>              Labels: pull-request-available, usability
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> I think we have more and more users who are thinking about using Protobuf for their state types.
> Right now, Protobuf isn't supported directly in Flink. The only way to use Protobuf for a type is to register it via Kryo: https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/custom_serializers.html.
> Likewise for Avro types, we should be able to natively support Protobuf, having a {{ProtobufSerializer}} that handles serialization of Protobuf types. The serializer should also write necessary information in its snapshot, to enable schema evolution for it in the future. For Protobuf, this should almost work out-of-the-box.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)