[
https://issues.apache.org/jira/browse/FLINK-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874528#comment-15874528
]
Jin Mingjian commented on FLINK-5692:
-------------------------------------
[~StephanEwen] If my understanding is not wrong, the goal of this option is
just to let users to know what the types should be provided with custom
serializers but actually not when their application running. Then they can
provide it explicitly rather than silent Kryo fallback by Flink in default.
For this goal, way #1 is enough.
> 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 later).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
