[
https://issues.apache.org/jira/browse/FLINK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323645#comment-17323645
]
Flink Jira Bot commented on FLINK-6802:
---------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> PojoSerializer does not create ConvertDeserializer for removed/added fields
> ---------------------------------------------------------------------------
>
> Key: FLINK-6802
> URL: https://issues.apache.org/jira/browse/FLINK-6802
> Project: Flink
> Issue Type: Improvement
> Components: API / Type Serialization System
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Till Rohrmann
> Assignee: Tzu-Li (Gordon) Tai
> Priority: Major
> Labels: stale-assigned
>
> When calling {{PojoSerializer#ensureCompatibility}}, the PojoSerializer
> checks for compatibility. Currently, the method only construct a
> ConvertDeserializer if the number of old and new pojo fields is exactly the
> same. However, given the {{TypeSerializerConfigurationSnapshots}} and the
> current set of fields, it should also be possible to construct a
> ConvertDeserializer if new fields were added or old fields removed from the
> Pojo. I think that we should add this functionality.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
