Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Wed, 7 Jun 2017 14:08:18 +0000 (UTC)
From: "Tzu-Li (Gordon) Tai (JIRA)" <jira@apache.org>
To: dev@flink.apache.org
Message-ID: <JIRA.13078008.1496844456000.18617.1496844498378@Atlassian.JIRA>
In-Reply-To: <JIRA.13078008.1496844456000@Atlassian.JIRA>
References: <JIRA.13078008.1496844456000@Atlassian.JIRA> <JIRA.13078008.1496844456976@jira-lw-us.apache.org>
Subject: [jira] [Created] (FLINK-6864) Remove confusing "invalid POJO type"
 messages from TypeExtractor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 07 Jun 2017 14:08:27 -0000

Tzu-Li (Gordon) Tai created FLINK-6864:
------------------------------------------

             Summary: 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


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.3.15#6346)