Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/5084#issuecomment-86835246
Yeah I agree with Sean and what pretty much everyone else said.
My feeling is that we don't want typical spark users to be relying on
unstable API's, else it creates a lot of upgrade friction for users and/or
pressure on maintainers to stabilize this stuff. We annotate things as unstable
and expose them for two reasons (a) to get feedback on new API's we intend to
stabilize shortly (b) to expose internal hooks that are meant for third party
integrations (similar to kernel modules) such as data sources, but not expected
to be needed by end users.
Exposing internal utilities for end users, IMO, it's just not a good idea.
I don't think slapping an annotation means that there is no cost to doing this.
Users will rely on this stuff and it will create upgrade friction, and this is
why we are careful about what we expose.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
