[
https://issues.apache.org/jira/browse/FLINK-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-944.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.6-incubating
Fixed via 5fa5e50205afb41ebc39f197da07e87c0fdd0334 and 9ecb6df76ca5e7a42d0d62b1c9dca41e9e7ecd1b
> 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
> Fix For: 0.6-incubating
>
>
> 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
