[jira] [Closed] (FLINK-6864) Remove confusing "invalid POJO type" messages from TypeExtractor

["Greg Hogan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-6864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Greg Hogan closed FLINK-6864.
-----------------------------
    Resolution: Implemented

master: 450b4241404055ed6638e354be421b83380827c5

> Remove confusing "invalid POJO type" messages from TypeExtractor
> ----------------------------------------------------------------
>
>                 Key: FLINK-6864
>                 URL: https://issues.apache.org/jira/browse/FLINK-6864
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Type Serialization System
>            Reporter: Tzu-Li (Gordon) Tai
>            Assignee: Fang Yong
>             Fix For: 1.5.0
>
>
> When a user's type cannot be treated as a POJO, the {{TypeExtractor}} will log warnings such as ".. must have a default constructor to be used as a POJO.", "  ... is not a valid POJO type because not all fields are valid POJO fields." in the {{analyzePojo}} method.
> These messages are often conceived as misleading for the user to think that the job should have failed, whereas in fact in these cases Flink just fallsback to Kryo and treat then as generic types. We should remove these messages, and at the same time improve the type serialization docs at [1] to explicitly inform what it means when Flink does / does not recognizes a user type as a POJO.
> [1] https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/types_serialization.html#rules-for-pojo-types



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)