Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/5565#issuecomment-94366735
Hey @nkronenfeld - simply put, we cannot make binary-incompatible changes
to API's in Spark due to our API guarantees, so this rules out many of your
proposed changes. This has been true since Spark 1.0. Basically code compiled
against older versions needs to work with newer ones, and that sometimes means
swallowing minor API inconsistencies.
If you'd like to add new versions of functions with more arguments, or add
shared parent interfaces in a way that is binary compatible, that's not a
violation of the policy. In those cases though, a JIRA might be helpful to sort
of summarize your high level thoughts.
---
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]
