[
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-unassigned stale-major (was: auto-unassigned)
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.
> 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: Major
> Labels: auto-unassigned, stale-major
>
> 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)
