You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2017/06/20 12:48:00 UTC
[jira] [Resolved] (FLINK-6922) Enum(Value)SerializerConfigSnapshot
uses Java serialization to store enum values
[ https://issues.apache.org/jira/browse/FLINK-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tzu-Li (Gordon) Tai resolved FLINK-6922.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.3.1
Fixed for master via f24a499b37515b43789ae23d83c1cd9eb2f827b3.
Fixed for 1.3.1 via 732d9c14252ebaded32b4d96cb25926e83254892.
> Enum(Value)SerializerConfigSnapshot uses Java serialization to store enum values
> --------------------------------------------------------------------------------
>
> Key: FLINK-6922
> URL: https://issues.apache.org/jira/browse/FLINK-6922
> Project: Flink
> Issue Type: Bug
> Components: Type Serialization System
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Till Rohrmann
> Assignee: Tzu-Li (Gordon) Tai
> Fix For: 1.3.1
>
>
> The {{EnumSerializer}} and the {{EnumValueSerializer}} (Scala) uses Java serialization to store enum values. From a user perspective this can be a bit of a problem if the user forgot to add a serial version UID. I think it would be better to store the enum information without Java serialization to avoid this problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)