Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2760#discussion_r18859740
--- Diff: project/MimaExcludes.scala ---
@@ -51,6 +51,19 @@ object MimaExcludes {
// MapStatus should be private[spark]
ProblemFilters.exclude[IncompatibleTemplateDefProblem](
"org.apache.spark.scheduler.MapStatus")
+ ) ++
+ Seq(
+ // Adding new methods to the JavaRDDLike trait:
+ ProblemFilters.exclude[MissingMethodProblem](
--- End diff --
The problem here is that JavaRDDLike is a trait, which compiles down to
both an abstract base class and an interface. Adding a method to an interface
may break binary compatibility for implementors of that interface. We don't
actually intend for anyone to implement JavaRDDLike and, in fact, there's no
reason that it should be a trait and not an abstract base class except for
backwards-compatibility.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
