You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "YangFei (JIRA)" <ji...@apache.org> on 2019/04/30 08:25:00 UTC

[jira] [Commented] (FLINK-10896) Extend state schema evolution support for more types

    [ https://issues.apache.org/jira/browse/FLINK-10896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830052#comment-16830052 ] 

YangFei commented on FLINK-10896:
---------------------------------

I have a question . The thrift is used widely in our project now. I can not change that because of a history reason. 

So ,how can I support my thrift state evolution ? Is there any good solutions now ?

> Extend state schema evolution support for more types
> ----------------------------------------------------
>
>                 Key: FLINK-10896
>                 URL: https://issues.apache.org/jira/browse/FLINK-10896
>             Project: Flink
>          Issue Type: New Feature
>          Components: API / Type Serialization System
>            Reporter: Tzu-Li (Gordon) Tai
>            Priority: Major
>
> Whether or not a state's schema can be evolved (e.g., removing / adding fields to a POJO-typed state, modifying an Avro-type state's schema, etc.) depends on whether or not the type's corresponding {{TypeSerializer}} and its {{TypeSerializerSnapshot}} properly supports it.
> As of Flink 1.7, we currently only have support for evolving Avro types (with FLINK-10605).
> This tracks the support for other composite types that would benefit from an evolvable schema, such as POJOs, tuples, Scala case classes etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)