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:47:00 UTC
[jira] [Resolved] (FLINK-6948) EnumValueSerializer cannot handle
removed enum values
[ https://issues.apache.org/jira/browse/FLINK-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tzu-Li (Gordon) Tai resolved FLINK-6948.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.3.1
Fixed for master via 228faf8c2a113de0dea366668e87484dbe7ec8b5.
Fixed for 1.3.1 via c10fb2bbb42f255dc14ded16d754db395385d441.
> EnumValueSerializer cannot handle removed enum values
> -----------------------------------------------------
>
> Key: FLINK-6948
> URL: https://issues.apache.org/jira/browse/FLINK-6948
> Project: Flink
> Issue Type: Bug
> Components: Type Serialization System
> Affects Versions: 1.3.1, 1.4.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Critical
> Fix For: 1.3.1
>
>
> The {{EnumValueSerializer}} cannot handle removed enum values or enum values whose ordinal value have been changed. We should try to detect these cases and require migration. The problem is that we take the values of the new enum and iterate over them without checking that all old enum values contained in the config snapshot are actually contained.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)