[
https://issues.apache.org/jira/browse/FLINK-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15143530#comment-15143530
]
Stephan Ewen commented on FLINK-2609:
-------------------------------------
Flink internally has its own POJO serializer and the KryoSerializer for certain
types. Both can make use of "pre-registering types (classes)" to serialize more
efficiently.
In the batch API, Flink traverses the entire dataflow graph and looks at all
TypeInformation, and checks all classes for types that may occur during
runtime. It registers those types at the POJO and KryoSerializer automatically.
The batch API code is here:
https://github.com/apache/flink/blob/master/flink-java/src/main/java/org/apache/flink/api/java/ExecutionEnvironment.java#L970
The streaming API should basically replicate this behavior.
> Automatic type registration is only called from the batch execution
> environment
> -------------------------------------------------------------------------------
>
> Key: FLINK-2609
> URL: https://issues.apache.org/jira/browse/FLINK-2609
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 0.10.0
> Reporter: Robert Metzger
>
> Kryo types in the streaming API are quite expensive to serialize because they
> are not automatically registered at Kryo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
