[
https://issues.apache.org/jira/browse/FLINK-10897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772678#comment-16772678
]
Tzu-Li (Gordon) Tai commented on FLINK-10897:
---------------------------------------------
Hi [~kisimple], I'm sorry but I just recalled that you were thinking about
working on this.
The problem right now is that, while resolving FLINK-11485, I realized that
supporting schema evolution was such a low-hanging fruit that I incorporated
within the same changes for that ticket.
Therefore, this PR: https://github.com/apache/flink/pull/7759 essentially also
fixes this ticket now.
I hope you haven't put too much effort into this ticket yet.
On the other hand, it would be great if you can help with the review for the
above PR.
Would be great if we manage to merge this for 1.8.0.
> Support POJO state schema evolution
> -----------------------------------
>
> Key: FLINK-10897
> URL: https://issues.apache.org/jira/browse/FLINK-10897
> Project: Flink
> Issue Type: Sub-task
> Components: Type Serialization System
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: boshu Zheng
> Priority: Major
>
> Main action point for this is to implement a separate POJO serializer that is
> specifically used as the restore serializer.
> This restore POJO serializer should be able to read and dump values of fields
> that no longer exists in the updated POJO schema, and assign default values
> to newly added fields. Snapshot of the {{PojoSerializer}} should contain
> sufficient information so that on restore, the information can be compared
> with the adapted POJO class to figure out which fields have been removed /
> added.
> Changing fields types is out of scope and should not be supported.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
