You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2021/08/27 07:36:00 UTC
[jira] [Updated] (FLINK-24017) Pin registration IDs of Java
serializers
[ https://issues.apache.org/jira/browse/FLINK-24017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler updated FLINK-24017:
-------------------------------------
Description:
We currently register a bunch of serializers with Kryo without specifying registration IDs. As a result we are locked in to a specific number of serializers.
In order to allow the KryoSerializer to be used without the Scala serializers being registered, we need to pin the registration IDs of our current java serializers. This also includes user-defined serializers in the execution config.
was:
We currently register a bunch of serializers with Kryo without specifying registration IDs. As a result we are locked in to a specific number of serializers.
In order to allow the KryoSerializer to be used without the Scala serializers being registered, we need to pin the registration IDs of our current java serializers.
> Pin registration IDs of Java serializers
> ----------------------------------------
>
> Key: FLINK-24017
> URL: https://issues.apache.org/jira/browse/FLINK-24017
> Project: Flink
> Issue Type: Sub-task
> Components: API / Type Serialization System
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Fix For: 1.15.0
>
>
> We currently register a bunch of serializers with Kryo without specifying registration IDs. As a result we are locked in to a specific number of serializers.
> In order to allow the KryoSerializer to be used without the Scala serializers being registered, we need to pin the registration IDs of our current java serializers. This also includes user-defined serializers in the execution config.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)