You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2015/11/30 16:31:11 UTC
[jira] [Closed] (FLINK-3088) WritableSerializer cannot copy
writable object
[ https://issues.apache.org/jira/browse/FLINK-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-3088.
--------------------------------
Resolution: Fixed
Fixed via 20ebad048d3b4621a6e801a4d24a15d4468f2ba6
> WritableSerializer cannot copy writable object
> ----------------------------------------------
>
> Key: FLINK-3088
> URL: https://issues.apache.org/jira/browse/FLINK-3088
> Project: Flink
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0, 0.10.1
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
>
> The {{WritableSerializer}}, {{ValueSerializer}}, {{AvroSerializer}}, {{WritableComparator}} and {{ValueComparator}} use plain {{Kryo}} instances to copy the objects. In cases where {{Kryo}} fails to copy the object, e.g. missing no-arg constructor, the serializer and comparator instances fail even though the objects are serializable.
> As a fallback strategy I propose to copy the objects by serializing and deserializing them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)