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

Flink Jira Bot updated FLINK-10896:
-----------------------------------
    Labels: stale-major  (was: )

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> 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
>              Labels: stale-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)

Reply via email to