You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2019/05/11 04:29:00 UTC
[jira] [Comment Edited] (SPARK-27681) Use scala.collection.Seq
explicitly instead of scala.Seq alias
[ https://issues.apache.org/jira/browse/SPARK-27681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837752#comment-16837752 ]
Marcelo Vanzin edited comment on SPARK-27681 at 5/11/19 4:28 AM:
-----------------------------------------------------------------
Also the change you're proposing likely would break source compatibility, which would make upgrading to Spark + Scala 2.13 harder than just a recompile...
was (Author: vanzin):
Also the change you're proposing likely would break source compatibility, which would make upgrading to Spark 3 harder than just a recompile...
> Use scala.collection.Seq explicitly instead of scala.Seq alias
> --------------------------------------------------------------
>
> Key: SPARK-27681
> URL: https://issues.apache.org/jira/browse/SPARK-27681
> Project: Spark
> Issue Type: Sub-task
> Components: ML, MLlib, Spark Core, SQL, Structured Streaming
> Affects Versions: 3.0.0
> Reporter: Sean Owen
> Assignee: Sean Owen
> Priority: Major
>
> {{scala.Seq}} is widely used in the code, and is an alias for {{scala.collection.Seq}} in Scala 2.12. It will become an alias for {{scala.collection.immutable.Seq}} in Scala 2.13. To avoid API changes, we should simply explicit import and use {{scala.collection.Seq}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org