Mohan,

You’ll need to register it; we register our serializer in lines 69 to 76 in 
https://github.com/bigdatagenomics/adam/blob/master/adam-core/src/main/scala/org/bdgenomics/adam/serialization/ADAMKryoRegistrator.scala.
 Our serializer implementation falls back on the default Avro serializer; you 
may want to look at Twitter’s Chill serializers, as they may have a higher 
performance Kryo serializer for Avro.

Regards,

Frank Austin Nothaft
fnoth...@berkeley.edu
fnoth...@eecs.berkeley.edu
202-340-0466

On Sep 18, 2014, at 8:43 AM, mohan.gadm <mohan.g...@gmail.com> wrote:

> Thanks for the info frank.
> so your suggestion could be to use Avro serializer.
> 
> i just have to configure it like Kryo for the same property? and is there
> any registering process for this or just specify serializer?
> Also does it effect performance. what measures to be taken to avoid.
> (im using kryo just because of its high performance, size compared to avro)
> 
> 
> 
> -----
> Thanks & Regards,
> Mohan
> --
> View this message in context: 
> http://apache-spark-user-list.1001560.n3.nabble.com/Kryo-fails-with-avro-having-Arrays-and-unions-but-succeeds-with-simple-avro-tp14549p14567.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
> For additional commands, e-mail: user-h...@spark.apache.org
> 

Reply via email to