[
https://issues.apache.org/jira/browse/FLINK-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224184#comment-15224184
]
ASF GitHub Bot commented on FLINK-2609:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1833#issuecomment-205307922
Let's not merge this as is, it uses again a static de-duplicator, like the
DataSet API used to (we recently eliminated that). These static utils to work
around putting adding variable in the right place is an antipattern.
Why not have the registration de-duplicator in the ExecutionEnvironment?
Since the ExecutionCondig is also one-per environment, and is always accessed
through the environment, that seems like the way to go...
> 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
> Assignee: Chesnay Schepler
>
> 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)
