[
https://issues.apache.org/jira/browse/SPARK-25075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837516#comment-16837516
]
Sean Owen commented on SPARK-25075:
-----------------------------------
OK, so we can possibly defer this by waiting until 2.13 support to go
explicitly import scala.collection.Seq everywhere rather than use the alias in
order to keep the type the same. I mean, we could get going on it now too;
that's a lot of imports!
Traversable: one usage is in a public API. We'll have to deprecate that and
replace with Iterable, then remove when 2.13 support is added. Likewise there
are some usages of removed collection classes, though so far looks all internal.
Right now I'm mostly interested in identifying changes we can't solve by
deprecating something in 3.x and then removing in 3.(x+1) to allow for 2.13
support. Probably nothing that will truly only be solvable in 4.x that I see so
far, but, maybe best to start on these changes before 3.0.
Anyone's welcome to; I may start pushing some minor proactive changes for 2.13.
> Build and test Spark against Scala 2.13
> ---------------------------------------
>
> Key: SPARK-25075
> URL: https://issues.apache.org/jira/browse/SPARK-25075
> Project: Spark
> Issue Type: Umbrella
> Components: Build, Project Infra
> Affects Versions: 3.0.0
> Reporter: Guillaume Massé
> Priority: Major
>
> This umbrella JIRA tracks the requirements for building and testing Spark
> against the current Scala 2.13 milestone.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
