You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2019/05/13 17:48:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Sean Owen updated SPARK-27681:
------------------------------
Description: {{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. In many cases, this will be fine, as Spark users using Scala 2.13 will also have this changed alias. In some cases it may be undesirable, as it will cause some code to compile in 2.12 but not in 2.13. In some cases, making the type {{scala.collection.Seq}} explicit so that it doesn't vary can help avoid this, so that Spark apps might cross-compile for 2.12 and 2.13 with the same source. (was: {{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}}.)
> 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. In many cases, this will be fine, as Spark users using Scala 2.13 will also have this changed alias. In some cases it may be undesirable, as it will cause some code to compile in 2.12 but not in 2.13. In some cases, making the type {{scala.collection.Seq}} explicit so that it doesn't vary can help avoid this, so that Spark apps might cross-compile for 2.12 and 2.13 with the same source.
--
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