> > Hey, I wanted to know why we have the SerializableSerializer when we
> > encounter an unregistered class and what advantage we get by using it over
> > the FieldsSerializer from kryo.
I may not be recalling correctly, so take this with a grain of salt:
>From my memory it was not there for per
Hi,
Actually, no idea because that particularly class dates back to 2012:
https://github.com/apache/storm/commit/4debef138e90053e692f72a761e3a3b6692ebe90
So 12+ years old ;-) - FieldSerializer in Kryo was introduced in 2012 too.
If you look into the mail archive, there is only a link towards:
h
Hey, I wanted to know why we have the SerializableSerializer when we
encounter an unregistered class and what advantage we get by using it over
the FieldsSerializer from kryo.
I did some very basic performance testing and the FieldsSerializer seems to
perform better than SerializableSerializer. I c
