[
https://issues.apache.org/jira/browse/FLINK-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6800:
----------------------------------
Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> PojoSerializer ignores added pojo fields
> ----------------------------------------
>
> Key: FLINK-6800
> URL: https://issues.apache.org/jira/browse/FLINK-6800
> Project: Flink
> Issue Type: Bug
> Components: API / Type Serialization System
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Till Rohrmann
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned
>
> The {{PojoSerializer}} contains a list of pojo fields which are represented
> as {{Field}} instances. Upon serialization the names of these fields are
> serialized. When being deserialized these names are used to look up the
> respective {{Fields}} of a dynamically loaded class. If the dynamically
> loaded class has additional fields (compared to when the serializer was
> serialized), then these fields will be ignored (for the read and for the
> write path). While this is necessary to read stored data, it is dangerous
> when writing new data, because all newly added fields won't be serialized.
> This subtleness is really hard to detect for the user. Therefore, I think we
> should eagerly fail if the newly loaded type contains new fields which
> haven't been present before.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
