You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "mingleizhang (JIRA)" <ji...@apache.org> on 2017/06/01 16:27:05 UTC

[jira] [Commented] (FLINK-6800) PojoSerializer ignores added pojo fields

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

mingleizhang commented on FLINK-6800:
-------------------------------------

What you mean is to add a exception detection mechanism for detecting the newly loaded type contains new fields which havent been present before ? If the mechanism detect that situation, then we should throw exception or try catch it. Right ?

> PojoSerializer ignores added pojo fields
> ----------------------------------------
>
>                 Key: FLINK-6800
>                 URL: https://issues.apache.org/jira/browse/FLINK-6800
>             Project: Flink
>          Issue Type: Bug
>          Components: Type Serialization System
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Till Rohrmann
>
> 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
(v6.3.15#6346)