[ https://issues.apache.org/jira/browse/SPARK-29292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026936#comment-17026936 ]
Sean R. Owen commented on SPARK-29292: -------------------------------------- Right, I agree. I can try updating my fork and pushing the commits to a branch, for evaluation in _2.12_ at least. I just wasn't bothering until it seemed like 2.13 support blockers were removed, to do it once. Happy to do it though if you want to play with it and/or just see the scope of the change. > Fix internal usages of mutable collection for Seq in 2.13 > --------------------------------------------------------- > > Key: SPARK-29292 > URL: https://issues.apache.org/jira/browse/SPARK-29292 > Project: Spark > Issue Type: Sub-task > Components: Spark Core > Affects Versions: 3.0.0 > Reporter: Sean R. Owen > Assignee: Sean R. Owen > Priority: Minor > > Kind of related to https://issues.apache.org/jira/browse/SPARK-27681, but a > simpler subset. > In 2.13, a mutable collection can't be returned as a > {{scala.collection.Seq}}. It's easy enough to call .toSeq on these as that > still works on 2.12. > {code} > [ERROR] [Error] > /Users/seanowen/Documents/spark_2.13/core/src/main/scala/org/apache/spark/ExecutorAllocationManager.scala:467: > type mismatch; > found : Seq[String] (in scala.collection) > required: Seq[String] (in scala.collection.immutable) > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org