Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9169#issuecomment-151396799
Thanks! On `@Experimental`, I assume it simply means that it is intended
for end users (i.e. not a `@DeveloperApi`) but may be removed or changed at any
time (without even deprecation).
While it seems nice to try to keep these stable or use deprecation, as you
say, it tends to make them act like stable methods. This can be a small problem
if an API is added under the theory that it's just `@Experimental` and is thus
low-risk, but is then treated like it can't be changed.
I imagine that most users don't pay a lot of attention to the tag, and
therefore might generally be surprised if such a method went away. I think all
of this simply argues for more rapidly reflecting reality: lots of
`@Experimental` methods are long since really stable and should be untagged.
This is a good first crack at that.
I'll put down a to-do to do the same for core and streaming, as I think
most of those tags can probably go.
---
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
