[
https://issues.apache.org/jira/browse/FLINK-9052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409135#comment-16409135
]
Truong Duc Kien commented on FLINK-9052:
----------------------------------------
Turn out this issue is due to Java API's inability to extract the correct type
tnformation for Scala object. I've attach a program demoing the problem.
The
[documents|https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/types_serialization.html#creating-a-typeinformation-or-typeserializer]
should be clearer about this. As is, I have the impression that the two APIs
are equivalent.
> Flink complains when scala.Option is used inside POJO
> -----------------------------------------------------
>
> Key: FLINK-9052
> URL: https://issues.apache.org/jira/browse/FLINK-9052
> Project: Flink
> Issue Type: Bug
> Components: Type Serialization System
> Affects Versions: 1.4.2
> Reporter: Truong Duc Kien
> Priority: Major
> Attachments: TypeInfomationTest.scala
>
>
> According to the documentation, Flink has a specialized serializer for Option
> type. However, when an Option field is used inside a POJO, the following
> WARNING appears in TaskManagers' log.
>
> {{No fields detected for class scala.Option. Cannot be used as a PojoType.
> Will be handled as GenericType}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
