This is a master list for MLlib improvements we plan to have in Spark 2.0. Please view this list as a wish list rather than a concrete plan, because we don't have an accurate estimate of available resources. Due to limited review bandwidth, features appearing on this list will get higher priority during code review. But feel free to suggest new items to the list in comments. We are experimenting with this process. Your feedback would be greatly appreciated.
- Please read https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark carefully. Code style, documentation, and unit tests are important.
- If you are a first-time Spark contributor, please always start with a starter task rather than a medium/big feature. Based on our experience, mixing the development process with a big feature usually causes long delay in code review.
- Never work silently. Let everyone know on the corresponding JIRA page when you start working on some features. This is to avoid duplicate work. For small features, you don't need to wait to get JIRA assigned.
- For medium/big features or features with dependencies, please get assigned first before coding and keep the ETA updated on the JIRA. If there exist no activity on the JIRA page for a certain amount of time, the JIRA should be released for other contributors.
- Do not claim multiple (>3) JIRAs at the same time. Try to finish them one after another.
- Remember to add the `@Since("2.0.0")` annotation to new public APIs.
- Please review others' PRs (https://spark-prs.appspot.com/#mllib). Code review greatly helps to improve others' code as well as yours.
- Try to break down big features into small and specific JIRA tasks and link them properly.
- Add a "starter" label to starter tasks.
- Put a rough estimate for medium/big features and track the progress.
- If you start reviewing a PR, please add yourself to the Shepherd field on JIRA.
- If the code looks good to you, please comment "LGTM". For non-trivial PRs, please ping a maintainer to make a final pass.
- After merging a PR, create and link JIRAs for Python, example code, and documentation if applicable.
This is NOT a complete list of MLlib JIRAs for 2.0. We only include umbrella JIRAs and high-level tasks.
Major efforts in this release:
- `spark.ml`: Achieve feature parity for the `spark.ml` API, relative to the `spark.mllib` API. This includes the Python API.
SPARK-13944) Linear algebra: Separate out the linear algebra library as a standalone project without a Spark dependency to simplify production deployment.
- Pipelines API: Complete critical improvements to the Pipelines API
- New features: As usual, we expect to expand the feature set of MLlib. However, we will prioritize API parity over new features. New algorithms should be written for `spark.ml`, not `spark.mllib`.
- iteratively re-weighted least squares (IRLS) for GLMs (
- estimator interface for GLMs (
- extended support for GLM model families and link functions in SparkR (
- improved model summaries and stats via IRLS (
Additional (maybe lower priority):
- robust linear regression with Huber loss (
- vector-free L-BFGS (
- tree partition by features (
- local linear algebra (
- weighted instance support (
- locality sensitive hashing (LSH) (
- deep learning (
- factorization machine (
- distributed LU decomposition (
- bivariate statistics as UDAFs (
- R-like statistics for GLMs (
- sketch algorithms (cross listed) : approximate quantiles (
SPARK-6761), count-min sketch ( SPARK-6763), Bloom filter ( SPARK-12818)
- pipeline persistence (
- ML attribute API improvements (
- predict single instance (
- test Kaggle datasets (
There may be other design improvement efforts for Pipelines, to be listed here soon. See (
SPARK-5874) for a list of possibilities.
- PMML export
- model save/load
- code generation
- decision tree and tree ensembles (
- decision tree and tree ensembles (
- public dataset loader (SPARK-10388)
The main goal of Python API is to have feature parity with Scala/Java API. You can find a complete list here. The tasks fall into two major categories:
- Pipeline persistence in PySpark (
- Python API for missing methods (
- Python API for new algorithms. Committers should create a JIRA for the Python API after merging a public feature in Scala/Java.
- support more families and link functions in SparkR::glm (
- model summary with R-like statistics for GLMs (
- support more algorithms (k-means (
SPARK-13011), survival analysis ( SPARK-13010), etc.)