Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-15581

MLlib 2.1 Roadmap

    XMLWordPrintableJSON

    Details

    • Type: Umbrella
    • Status: Closed
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.1.0
    • Component/s: ML, MLlib
    • Labels:
    • Target Version/s:

      Description

      This is a master list for MLlib improvements we are working on for the next release. Please view this as a wish list rather than a definite plan, for 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.

      Instructions

      For contributors:

      • 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("VERSION")` 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.

      For committers:

      • 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.

      Roadmap (WIP)

      This is NOT a complete list of MLlib JIRAs for 2.1. We only include umbrella JIRAs and high-level tasks.

      Major efforts in this release:

      • Feature parity for the DataFrames-based API (`spark.ml`), relative to the RDD-based API
      • ML persistence
      • Python API feature parity and test coverage
      • R API expansion and improvements
      • Note about new features: As usual, we expect to expand the feature set of MLlib. However, we will prioritize API parity, bug fixes, and improvements over new features.

      Note `spark.mllib` is in maintenance mode now. We will accept bug fixes for it, but new features, APIs, and improvements will only be added to `spark.ml`.

      Critical feature parity in DataFrame-based API

      Persistence

      • Complete persistence within MLlib
      • MLlib in R format: compatibility with other languages (SPARK-15572)
      • Impose backwards compatibility for persistence (SPARK-15573)

      Python API

      • Standardize unit tests for Scala and Python to improve and consolidate test coverage for Params, persistence, and other common functionality (SPARK-15571)
      • Improve Python API handling of Params, persistence (SPARK-14771) (SPARK-14706)
        • Note: The linked JIRAs for this are incomplete. More to be created...
        • Related: Implement Python meta-algorithms in Scala (to simplify persistence) (SPARK-15574)
      • Feature parity: The main goal of the Python API is to have feature parity with the Scala/Java API. You can find a complete list here. The tasks fall into two major categories:
        • Python API for missing methods (SPARK-14813)
        • Python API for new algorithms. Committers should create a JIRA for the Python API after merging a public feature in Scala/Java.

      SparkR

      • Improve R formula support and implementation (SPARK-15540)
      • Various SparkR ML API and usability improvements
        • Note: No linked JIRA yet, but need to create an umbrella once more issues are collected.
      • Wrap more MLlib algorithms (SPARK-16442)
      • Release SparkR on CRAN SPARK-15799

      Pipeline API

      Algorithms and performance

      Additional (may be lower priority):

      Other

      • Infra
      • public dataset loader (SPARK-10388)
      • Documentation: improve organization of user guide (SPARK-8517)
      • Python Documentation: expose default values of params in some way (SPARK-15130)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                josephkb Joseph K. Bradley
              • Votes:
                0 Vote for this issue
                Watchers:
                47 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: