Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/17867
Yeah, that's because we didn't always do that in time, especially for
spark.mllib packages which has been in maintenance mode. But for spark.ml
package, I think we always keep to remove methods deprecated in last
feature/minor release. And we have already warned ```This method is deprecated
and will be removed in 2.2.0``` in API documents, it may confuse users if we
don't take action follow the API annotation. I'm prefer to merge this as the
old convention, and start the new convention in the following release which we
should add annotation like ```deprecated and will be removed in 3.0.0```. What
do you think about it? Thanks.
---
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]
