[
https://issues.apache.org/jira/browse/SPARK-14221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477922#comment-15477922
]
Josh Rosen commented on SPARK-14221:
------------------------------------
Assuming that the license is the same, I don't see any reason why we couldn't
upgrade to Kryo aside from issues if Kryo 4 can't read Kryo 2 files and users
happen to rely on our bundled version of Kryo to permanently persist their
data. I'm pretty sure that the documentation for Spark's own Serializer
stresses that it should not be used for cross-version-compatible / portable
data persistence / serialization. As long as we shade our own Kryo to let users
continue to use their own version in their app then I think we should be okay.
> Cross-publish Chill for Scala 2.12
> ----------------------------------
>
> Key: SPARK-14221
> URL: https://issues.apache.org/jira/browse/SPARK-14221
> Project: Spark
> Issue Type: Sub-task
> Components: Build
> Reporter: Josh Rosen
> Assignee: Josh Rosen
>
> We need to cross-publish Chill in order to build against Scala 2.12.
> Upstream issue: https://github.com/twitter/chill/issues/252
> I tried building and testing {{chill-scala}} against 2.12.0-M3 and ran into
> multiple failed tests due to issues with Java8 lambda serialization (similar
> to https://github.com/EsotericSoftware/kryo/issues/215), so this task will be
> slightly more involved then just bumping the dependencies in the Chill build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
