Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/22977
I think one major issue is, there is no document about how to update mima
with new releases. Anyone knows the detailed process? Seems we need to update
`MimaExcludes.scala` with something like `lazy val v30excludes = v24excludes ++
Seq` when cut the new branch, and update `MimaBuild.scala` when the new release
is published.
And there are 2 remaining issues.
1. the data source v2 changes broke a lot of mima rules, while I expect
interfaces marked as "Envolving" should not be tracked by mima.
2. mllib broke a lot of mima rules, seems caused by
https://github.com/apache/spark/pull/22921 . @srowen can you take a look?
Also cc @JoshRosen @gatorsmile @shaneknapp @vanzin @holdenk @felixcheung
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
