You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Gabor Gevay (JIRA)" <ji...@apache.org> on 2015/07/30 17:39:04 UTC
[jira] [Created] (FLINK-2437) TypeExtractor.analyzePojo has some
problems around the default constructor detection
Gabor Gevay created FLINK-2437:
----------------------------------
Summary: TypeExtractor.analyzePojo has some problems around the default constructor detection
Key: FLINK-2437
URL: https://issues.apache.org/jira/browse/FLINK-2437
Project: Flink
Issue Type: Bug
Components: Type Serialization System
Reporter: Gabor Gevay
Assignee: Gabor Gevay
Priority: Minor
If a class does have a default constructor, but the user forgot to make it public, then TypeExtractor.analyzePojo still thinks everything is OK, so it creates a PojoTypeInfo. Then PojoSerializer.createInstance blows up.
Furthermore, a "return null" seems to be missing from the then case of the if after catching the NoSuchMethodException which would also cause a headache for PojoSerializer.
An additional minor issue is that the word "class" is printed twice in several places, because class.toString also prepends it to the class name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)