flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5692) Add an Option to Deactivate Kryo Fallback for Serializers
Date Mon, 20 Feb 2017 16:05:44 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874749#comment-15874749

Stephan Ewen commented on FLINK-5692:

[~jinmingjian] That right, #1 approach would work for a start

> Add an Option to Deactivate Kryo Fallback for Serializers
> ---------------------------------------------------------
>                 Key: FLINK-5692
>                 URL: https://issues.apache.org/jira/browse/FLINK-5692
>             Project: Flink
>          Issue Type: New Feature
>          Components: Type Serialization System
>    Affects Versions: 1.2.0
>            Reporter: Stephan Ewen
>              Labels: easyfix, starter
> Some users want to avoid that Flink's serializers use Kryo, as it can easily become a
hotspot in serialization.
> For those users, it would help if there is a flag to "deactive generic types". Those
users could then see where types are used that default to Kryo and change these types (make
them PoJos, Value types, or write custom serializers).
> There are two ways to approach that:
>   1. (Simple) Make {{GenericTypeInfo}} threw an exception whenever it would create a
Kryo Serializer (when the respective flag is set in the {{ExecutionConfig}})
>   2. Have a static flag on the {{TypeExtractor}} to throw an exception whenever it would
create a {{GenericTypeInfo}}. This approach has the downside of introducing some static configuration
to the TypeExtractor, but may be more helpful because it throws exceptions in the programs
at points where the types are used (not where the serializers are created, which may be much

This message was sent by Atlassian JIRA

View raw message