Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9667#issuecomment-169134436
There has been a lot of confusion about the spark.ml vs spark.mllib APIs,
so we want to achieve feature parity in spark.ml. There are no set plans to
deprecate spark.mllib, but it will presumably be replaced by spark.ml
eventually; a date could be discussed after we achieve feature parity.
However, we would definitely keep and maintain spark.mllib for a long time to
support existing workloads.
---
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
