Hi Martin,
no, Kryo is actually only used for copying the element. For
serialization/deserialization the write and readFields methods are used.
I’ve changed it now that if Kryo fails, then it will serialize the object
into a byte array and deserialize it from there again in order to copy the
eleme
Hi Till!
Thanks for looking into it. Is it correct to assume that when a user
defined class that implements Writable is used in Flink datasets, it's
always serialized using Kryo even if the members of that class could be
serialized by Flink's own serialization mechanism?
Again, thanks.
Best,
Mar
The issue is https://issues.apache.org/jira/browse/FLINK-3088.
On Fri, Nov 27, 2015 at 12:21 PM, Till Rohrmann
wrote:
> Hi Martin,
>
> I think the problem is that the the WritableSerializer, WritableComparator,
> ValueComparator, ValueSerializer and the AvroSerializer all use Kryo to
> copy obje
Hi Martin,
I think the problem is that the the WritableSerializer, WritableComparator,
ValueComparator, ValueSerializer and the AvroSerializer all use Kryo to
copy objects. However, in some cases, e.g. missing no-arg constructor, Kryo
is not able to copy the object. In these cases, one should try
Hi,
I looked further into the problem and discovered, that the serialization
also fails for TestEnvironment and LocalEnvironment if a groupBy
operation is involved.
Please have a look at the updated Gist
https://gist.github.com/s1ck/566796df5f35ee1de6f9
Best,
Martin
On 27.11.2015 10:20, Ma
Hi,
While building IT tests which extend MultipleProgramsTestBase, I
encountered a problem with serialization:
I posted a minimal example here:
https://gist.github.com/s1ck/566796df5f35ee1de6f9
This runs fine with LocalEnvironment. However, when executing this in
CollectionEnvironment, it le
