Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16739
I've commented elsewhere, but wanted to here just to make more people
aware: Let's refrain from backporting new APIs into patch versions unless they
are really critical. We do not do this elsewhere in Spark, and we should not
in SparkR. New APIs and API changes should only happen in minor versions (and
ideally changes will only happen in major ones). It's been discussed elsewhere
that SparkR is more experimental than other parts of Spark, but the sooner we
start treating it like a stable library, the sooner it will be a stable
library. For most people, there isn't a huge difference between getting a new
API in a patch version (every 1-2 months) vs. getting it in a minor version
(every 4 months). Thanks all!
---
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]
