[SPARK-35142][PYTHON][ML][3.1] Fix incorrect return type for rawPredictionUDF in OneVsRestModel
#32269
Conversation
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
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
harupy
changed the title
harupy
changed the title
rawPredictionUDF in OneVsRestModel
harupy
changed the title
rawPredictionUDF in OneVsRestModel
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
HyukjinKwon
changed the title
rawPredictionUDF in OneVsRestModel
Member
|
Okay, this is actually already ported back to branch-3.1. Can you prepare a backport to branch-3.0 too? |
|
Test build #137723 has finished for PR 32269 at commit
|
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 PR backports #32245.
Fixes incorrect return type for
rawPredictionUDFinOneVsRestModel.Why are the changes needed?
Bugfix
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit test.