for Kryo right now.
>
>
>
>
>
> *From:* Stephan Ewen [mailto:se...@apache.org]
> *Sent:* Tuesday, March 07, 2017 6:21 AM
> *To:* user@flink.apache.org
> *Subject:* Re: Serialization performance
>
>
>
> Hi Billy!
>
>
>
> Out of curiosity: Were you ab
Hi Billy,
on the Beam side, you probably have looked into writing your own Coder
(the equivalent of a TypeSerializer in Flink). If yes, did that not work
out for you? And if yes, why?
Best,
Aljoscha
On Thu, Mar 2, 2017, at 22:02, Stephan Ewen wrote:
> Hi!
>
> I can write some more deta
s.toString();
>
>builder = *null*;
>
>*this*.comment = comment;
>
>
>
>GRKryoSerializer.*preregisterSchema*(comment, s);
>
> }
>
>
>
> *public* *synchronized* GenericRecordBuilder getBuilder()
>
> {
>
e.org]
Sent: Thursday, March 02, 2017 3:07 PM
To: user@flink.apache.org; Aljoscha Krettek
Subject: Re: Serialization performance
Hi!
Thanks for this writeup, very cool stuff !
For part (1) - serialization: I think that can be made a bit nicer. Avro is a
bit of an odd citizen in Flink, because Flink
Hi!
Thanks for this writeup, very cool stuff !
For part (1) - serialization: I think that can be made a bit nicer. Avro is
a bit of an odd citizen in Flink, because Flink serialization is actually
schema aware, but does not integrate with Avro. That's why Avro types go
through Kryo.
We should tr
