You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Fangchen Li (Jira)" <ji...@apache.org> on 2026/07/16 23:51:00 UTC
[jira] [Updated] (SPARK-55152) Evaluate serialization strategy for Scala 3 support
[ https://issues.apache.org/jira/browse/SPARK-55152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fangchen Li updated SPARK-55152:
--------------------------------
Description:
The current Kryo serialization depends on Twitter's chill library, which has no Scala 3 support and is unmaintained (last release: June 2021).
We have a few options here:
# Fork chill and take on its maintenance. This requires the least change in Spark, but adds extra responsibility and maintenance burden. Update: I forked chill and did a full update. The link: [https://github.com/forge-labs-dev/chill]. I'm not sure what to do with this fork yet. I'll try to get in touch with someone in X and have it merged back. Update: chill at its current state might work with Scala 3. N
# Switch to [scala-kryo-serialization|https://github.com/altoo-ag/scala-kryo-serialization], which supports Scala 3 but requires Kryo 5.
# Consider adding [Apache Fory|https://github.com/apache/fory] as an alternative serializer. It's much better maintained and much faster than Kryo. But we probably still need to keep Kryo for backward compatibility.
was:
The current Kryo serialization depends on Twitter's chill library, which has no Scala 3 support and is unmaintained (last release: June 2021).
We have a few options here:
# Fork chill and take on its maintenance. This requires the least change in Spark, but adds extra responsibility and maintenance burden. Update: I forked chill and did a full update. The link: [https://github.com/forge-labs-dev/chill]. I'm not sure what to do with this fork yet. I'll try to get in touch with someone in X and have it merged back.
# Switch to [scala-kryo-serialization|https://github.com/altoo-ag/scala-kryo-serialization], which supports Scala 3 but requires Kryo 5.
# Consider adding [Apache Fory|https://github.com/apache/fory] as an alternative serializer. It's much better maintained and much faster than Kryo. But we probably still need to keep Kryo for backward compatibility.
> Evaluate serialization strategy for Scala 3 support
> ---------------------------------------------------
>
> Key: SPARK-55152
> URL: https://issues.apache.org/jira/browse/SPARK-55152
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 4.2.0
> Reporter: Fangchen Li
> Priority: Major
>
> The current Kryo serialization depends on Twitter's chill library, which has no Scala 3 support and is unmaintained (last release: June 2021).
>
> We have a few options here:
> # Fork chill and take on its maintenance. This requires the least change in Spark, but adds extra responsibility and maintenance burden. Update: I forked chill and did a full update. The link: [https://github.com/forge-labs-dev/chill]. I'm not sure what to do with this fork yet. I'll try to get in touch with someone in X and have it merged back. Update: chill at its current state might work with Scala 3. N
> # Switch to [scala-kryo-serialization|https://github.com/altoo-ag/scala-kryo-serialization], which supports Scala 3 but requires Kryo 5.
> # Consider adding [Apache Fory|https://github.com/apache/fory] as an alternative serializer. It's much better maintained and much faster than Kryo. But we probably still need to keep Kryo for backward compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org