I understand that it affects performance, but for now the library that I am trying to use has some issues with Kryo. So I have no choice but to use Java Serializer for serializing objects of that library.
Okay, I can use this too. Currently I am using FieldSerializer annotation. I'll keep in mind to post such questions on users@apex. Thank You. On Tue, Feb 7, 2017 at 1:40 AM, Vlad Rozov <v.ro...@datatorrent.com> wrote: > Kryo allows to delegate serialization to Java. Add > "@DefaultSerializer(JavaSerializer.class)" > to a tuple class definition. As Santosh already mentioned, using Java > serializer is not recommended as it affect performance. > > I would recommend in the future to post similar questions on the user@apex. > dev@apex is used to discuss development of the platform and the library. > > Thank you, > > Vlad > > *Join us at Apex Big Data World-San Jose > <http://www.apexbigdata.com/san-jose.html>, April 4, 2017* > [image: http://www.apexbigdata.com/san-jose-register.html] > <http://www.apexbigdata.com/san-jose-register.html> > On 2/5/17 22:34, Ambarish Pande wrote: > > This is exactly what i wanted. > Thank You. > > On Mon, Feb 6, 2017 at 11:35 AM, Hitesh Kapoor <hit...@datatorrent.com> > <hit...@datatorrent.com> > wrote: > > > Hi Ambarish, > > Yes you can plug in your own serializer. You will have to set the > "STREAM_CODEC" port attribute to achieve the same. > You can refer xmlParserApplication from examples repo > (https://github.com/DataTorrent/examples). > > Regards, > Hitesh > > > On Mon, Feb 6, 2017 at 11:07 AM, Ambarish Pande > <ambarish.pande2...@gmail.com> wrote: > > > Hello, > > Is there a way to set up JAVA Serializer as the default serializer to be > used for a particular application. Currently, Kryo is the default > serializer and the library that I am using has compatibility issues with > Kryo. > > Thank You. > > > >
