[
https://issues.apache.org/jira/browse/SPARK-32398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247545#comment-17247545
]
Sean R. Owen commented on SPARK-32398:
--------------------------------------
Yes it did. It's just how it goes, I think. I continue to hope that these
API-breaking changes won't continue, so, updating to the latest version now
should help future-proof the code. But yes seems like we had to to buy 2.13
compatibility.
> Upgrade to scalatest 3.2.0 for Scala 2.13.3 compatibility
> ---------------------------------------------------------
>
> Key: SPARK-32398
> URL: https://issues.apache.org/jira/browse/SPARK-32398
> Project: Spark
> Issue Type: Sub-task
> Components: ML, Spark Core, SQL, Structured Streaming, Tests
> Affects Versions: 3.0.0
> Reporter: Sean R. Owen
> Assignee: Sean R. Owen
> Priority: Major
> Fix For: 3.1.0
>
>
> We'll need to update to scalatest 3.2.0 in order to pick up the fix here,
> which fixes an incompatibility with Scala 2.13.3:
> https://github.com/scalatest/scalatest/commit/7c89416aa9f3e7f2730a343ad6d3bdcff65809de
> That's a big change unfortunately - 3.1 / 3.2 reorganized many classes.
> Fortunately it's just like import updates in 100 files.
--
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
