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

Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2018/11/15 10:50:00 UTC

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

Tzu-Li (Gordon) Tai created FLINK-10896:
-------------------------------------------

             Summary: Extend state schema evolution support for more composite types
                 Key: FLINK-10896
                 URL: https://issues.apache.org/jira/browse/FLINK-10896
             Project: Flink
          Issue Type: New Feature
          Components: Type Serialization System
            Reporter: Tzu-Li (Gordon) Tai


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)