Thanks for the pointer Ken. As far as I know, we’re using the
StdInstantiatorStrategy as the fallback instantiator strategy for our Kryo
instances.
Cheers,
Till
On Fri, Feb 19, 2016 at 12:39 AM, Ken Krugler
wrote:
> I've seen this type of error when using Kryo with a Cascading scheme
>
I've seen this type of error when using Kryo with a Cascading scheme I'd
created.
In my case it happened when serializing a large object graph, where some of the
classes didn't have no-arg constructors.
The general fix was to set an instantiator strategy for Kryo - see:
https://github.com/Scal