[
https://issues.apache.org/jira/browse/FLINK-10896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061400#comment-17061400
]
Tzu-Li (Gordon) Tai commented on FLINK-10896:
---------------------------------------------
[~alpinegizmo] [~stevenz3wu]
I think evolution for Scala case classes has indeed came up quite a few times.
Whether or not this is possible still needs some deeper investigation though.
I'm not aware of anyone working on this right 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
(v8.3.4#803005)
