You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2019/12/03 17:00:08 UTC
[jira] [Resolved] (SPARK-30012) Change classes extending scala
collection classes to work with 2.13
[ https://issues.apache.org/jira/browse/SPARK-30012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun resolved SPARK-30012.
-----------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 26728
[https://github.com/apache/spark/pull/26728]
> Change classes extending scala collection classes to work with 2.13
> -------------------------------------------------------------------
>
> Key: SPARK-30012
> URL: https://issues.apache.org/jira/browse/SPARK-30012
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core, SQL
> Affects Versions: 3.0.0
> Reporter: Sean R. Owen
> Assignee: Sean R. Owen
> Priority: Minor
> Fix For: 3.0.0
>
>
> Several classes in the code base extend Scala collection classes, like:
> - ExternalAppendOnlyMap
> - CaseInsensitiveMap
> - AttributeMap
> - (probably more I haven't gotten to yet)
> The collection hierarchy changed in 2.13, and like elsewhere, I don't see that it's possible to use a compat library or clever coding to bridge the difference. I think we need to maintain two implementations in parallel source trees, possibly with a common ancestor with the commonalities.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org