Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9488#issuecomment-155530377
LGTM.
> It looks reasonable, and is not even something we'd have to wait for 2.0
for. I recall that we had not done this yet, and targeted it for 2.0, because
it required modifying the trait JavaRDDLike and that itself could break anyone
who (unusually) extended the trait. I think that's mitigated by
AbstractJavaRDDLike now though. Maybe @JoshRosen can give a thumbs up. In any
event I think you need a MiMa exclude to assure the build that this change is
OK. I think you could even record that it's effective as of "1.6.0" until we
know otherwise.
If we really don't want to break anything now, how about just adding new
methods to `AbstractJavaRDDLike`?
---
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]
