diff options
| author | Xiangrui Meng <meng@databricks.com> | 2015-01-14 17:50:33 -0800 |
|---|---|---|
| committer | Xiangrui Meng <meng@databricks.com> | 2015-01-14 17:50:33 -0800 |
| commit | 13d2406781714daea2bbf3bfb7fec0dead10760c (patch) | |
| tree | 9b236d11a954700c90c9f10c5d3d03511fe84dd9 /sql | |
| parent | 76389c5b99183e456ff85fd92ea68d95c4c13e82 (diff) | |
| download | spark-13d2406781714daea2bbf3bfb7fec0dead10760c.tar.gz spark-13d2406781714daea2bbf3bfb7fec0dead10760c.tar.bz2 spark-13d2406781714daea2bbf3bfb7fec0dead10760c.zip | |
[SPARK-5254][MLLIB] Update the user guide to position spark.ml better
The current statement in the user guide may deliver confusing messages to users. spark.ml contains high-level APIs for building ML pipelines. But it doesn't mean that spark.mllib is being deprecated.
First of all, the pipeline API is in its alpha stage and we need to see more use cases from the community to stabilizes it, which may take several releases. Secondly, the components in spark.ml are simple wrappers over spark.mllib implementations. Neither the APIs or the implementations from spark.mllib are being deprecated. We expect users use spark.ml pipeline APIs to build their ML pipelines, but we will keep supporting and adding features to spark.mllib. For example, there are many features in review at https://spark-prs.appspot.com/#mllib. So users should be comfortable with using spark.mllib features and expect more coming. The user guide needs to be updated to make the message clear.
Author: Xiangrui Meng <meng@databricks.com>
Closes #4052 from mengxr/SPARK-5254 and squashes the following commits:
6d5f1d3 [Xiangrui Meng] typo
0cc935b [Xiangrui Meng] update user guide to position spark.ml better
Diffstat (limited to 'sql')
0 files changed, 0 insertions, 0 deletions