The main reason is that it doesn't always work (e.g. sometimes application
program has special serialization / externalization written already for
Java which don't work in Kryo).
On Mon, May 12, 2014 at 5:47 PM, Anand Avati av...@gluster.org wrote:
Hi,
Can someone share the reason why Kryo
On Mon, May 12, 2014 at 2:47 PM, Anand Avati av...@gluster.org wrote:
Hi,
Can someone share the reason why Kryo serializer is not the default?
why should it be?
On top of it, the only way to serialize a closure into the backend (even
now) is java serialization (which means java serialization
Hi,
Can someone share the reason why Kryo serializer is not the default? Is
there anything to be careful about (because of which it is not enabled by
default)?
Thanks!
It was just because it might not work with some user data types that are
Serializable. But we should investigate it, as it’s the easiest thing one can
enable to improve performance.
Matei
On May 12, 2014, at 2:47 PM, Anand Avati av...@gluster.org wrote:
Hi,
Can someone share the reason why
As an example of where it sometimes doesn't work, in older versions of Kryo
/ Chill the Joda LocalDate class didn't serialize properly --
https://groups.google.com/forum/#!topic/cascalog-user/35cdnNIamKU
On Mon, May 12, 2014 at 4:39 PM, Reynold Xin r...@databricks.com wrote:
The main reason is
