Thanks guys for your answers, that is exactly information I was looking
for.
Krzysztof
2015-12-01 19:22 GMT+01:00 Robert Metzger :
> Hi Flavio,
>
> 1. you don't have to register serializers if its working for you. I would
> add a custom serializer if its not working or if the performance is poor
Hi Flavio,
1. you don't have to register serializers if its working for you. I would
add a custom serializer if its not working or if the performance is poor.
2. I don't think that there is such a performance comparison. Tuples are a
little faster than POJOs, other types (serialized with Kryo's st
Sorry for the long question but I take advantage of this discussion to ask
for something I've never fully understood.. Let's say I have for example a
thrift/protobuf/avro object Person.
1. Do I have really to register a custom serializer? In my code I create
a dataset from parquet-thrift but
Also, we don't add serializers automatically for DataStream programs. I've
opened a JIRA for this a while ago.
On Tue, Dec 1, 2015 at 10:20 AM, Till Rohrmann wrote:
> Hi Kryzsztof,
>
> it's true that we once added the Protobuf serializer automatically.
> However, due to versioning conflicts (see
Hi Kryzsztof,
it's true that we once added the Protobuf serializer automatically.
However, due to versioning conflicts (see
https://issues.apache.org/jira/browse/FLINK-1635), we removed it again. Now
you have to register the ProtobufSerializer manually:
https://ci.apache.org/projects/flink/flink-d
Hi!
I'm trying to use generated Protobuf wrappers compiled with protoc and pass
them as objects between functions of Flink. I'm using Flink 0.10.0.
Unfortunately, I get an exception on runtime:
[...]
Caused by: com.esotericsoftware.kryo.KryoException:
java.lang.UnsupportedOperationException
Serial
