[jira] [Resolved] (FLINK-5692) Add an Option to Deactivate Kryo Fallback for Serializers

["Stephan Ewen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Ewen resolved FLINK-5692.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

Fixed in 0f99aae1e1f8b693c2ba79a061046bc042113f0b with small followups in d498cbedfda7c5ebabbc5f8203d7518926ede423

> 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
>            Assignee: Jin Mingjian
>              Labels: easyfix, starter
>             Fix For: 1.3.0
>
>
> 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 later).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)