Github user tdas commented on the issue:
https://github.com/apache/spark/pull/13998
[Sorry! I missed the comment in the other PR]
Why would the user code break at runtime if the method with default
implementation ensures the same behavior as before?
We have been relying on this for many of our APIs. Methods have been added
to Receiver APIs. Hadoop has added a new methods overtime in their FileSystem
APIs. This is used fundamentally everywhere!
There is no cost for doing this now, and leaves room to take the decision
in the future of whether to add new functionality in the same API or make new
API.
---
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]
