[
https://issues.apache.org/jira/browse/SPARK-12414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238787#comment-15238787
]
Sean Owen commented on SPARK-12414:
-----------------------------------
Hm, I am not sure this was intended to allow third party serialized but to
choose among the ones in Spark. I think there would be class loader
complications and trouble with serializers having to know about internal Spark
classes. If you want to try anyway can you have your classes implement custom
serialization via Java's mechanism?
> Remove closure serializer
> -------------------------
>
> Key: SPARK-12414
> URL: https://issues.apache.org/jira/browse/SPARK-12414
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 1.0.0
> Reporter: Andrew Or
> Assignee: Sean Owen
> Fix For: 2.0.0
>
>
> There is a config `spark.closure.serializer` that accepts exactly one value:
> the java serializer. This is because there are currently bugs in the Kryo
> serializer that make it not a viable candidate. This was uncovered by an
> unsuccessful attempt to make it work: SPARK-7708.
> My high level point is that the Java serializer has worked well for at least
> 6 Spark versions now, and it is an incredibly complicated task to get other
> serializers (not just Kryo) to work with Spark's closures. IMO the effort is
> not worth it and we should just remove this documentation and all the code
> associated with it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
