You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2014/06/17 15:06:02 UTC

[jira] [Created] (FLINK-944) Serialization problem of CollectionInputFormat

Till Rohrmann created FLINK-944:
-----------------------------------

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