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 2019/01/15 10:52:00 UTC

[jira] [Commented] (FLINK-10897) Support POJO state schema evolution

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

Tzu-Li (Gordon) Tai commented on FLINK-10897:
---------------------------------------------

Hi [~kisimple], can you briefly explain how you plan to approach this?

> 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)