[SPARK-18291][SparkR][ML][FOLLOW-UP] Encode probability to prediction by SQLTransformer.#16058
Closed
yanboliang wants to merge 1 commit into
Closed
[SPARK-18291][SparkR][ML][FOLLOW-UP] Encode probability to prediction by SQLTransformer.#16058yanboliang wants to merge 1 commit into
yanboliang wants to merge 1 commit into
Conversation
Contributor
Author
|
Test build #69320 has finished for PR 16058 at commit
|
Member
|
LGTM |
Contributor
Author
|
Since we decided revert SPARK-18291 for 2.1 and add it back after SPARK-18618 resolved, I can directly add this change at that time. So I will close this PR. Thanks for reviewing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What changes were proposed in this pull request?
This is follow-up for #15788,
spark.glmcan encode probability to prediction bySQLTransformerrather than reimplementing a new transformer.How was this patch tested?
Existing tests.