[MLLIB] [WIP] [SPARK-3702] Standardizing abstractions and developer API for prediction #3427
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is WIP effort to standardize abstractions and developer API for prediction tasks (classification and regression) for the new ML api (org.apache.spark.ml).
Please refer to [https://issues.apache.org/jira/browse/SPARK-3702] for some discussion on design, and this design doc for major design decisions.
This is not intended to cover all algorithms; e.g., one big missing item is porting the GeneralizedLinearModel class to the new API. But it hopefully lays a fair amount of groundwork.
I have included a limited number of concrete classes in this WIP PR, for purposes of illustration:
Items remaining:
General plan for splitting into multiple PRs, in order:
Thanks to @epahomov and @BigCrunsh for input, including from [https://github.com//pull/2137] which improves upon the org.apache.spark.mllib APIs.
CC: @etrain @shivaram @mengxr