[
https://issues.apache.org/jira/browse/FLINK-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036152#comment-14036152 ]
ASF GitHub Bot commented on FLINK-944:
--------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-flink/pull/25> Serialization problem of CollectionInputFormat
> ----------------------------------------------
>
> Key: FLINK-944
> URL:
https://issues.apache.org/jira/browse/FLINK-944> Project: Flink
> Issue Type: Bug
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
>
> The CollectionInputFormat uses only the standard serialization means provided by the JVM. Thus data types which are serializable with a TypeSerializer but does not implement the Serializable interface cannot be used with a CollectionDataSource. Even worse, if one uses an aggregation type such as a tuple, only the top level object will be checked for serializability. Consequently, it will crash at runtime.
> It would be more user friendly to not enforce that a used data type has to implement the Serializable interface. Instead we should use the generated TypeSerializer to do the serialization. That way, we are more flexible.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Locked
