flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-2437) TypeExtractor.analyzePojo has some problems around the default constructor detection
Date Wed, 12 Aug 2015 10:32:45 GMT

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

Maximilian Michels closed FLINK-2437.
-------------------------------------
    Resolution: Fixed

> 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
>    Affects Versions: 0.10, 0.9.0
>            Reporter: Gabor Gevay
>            Assignee: Gabor Gevay
>            Priority: Minor
>             Fix For: 0.10, 0.9.1
>
>
> 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)

Mime
View raw message