Uh oh!
There was an error while loading. Please reload this page.
[SPARK-35278][SQL][2.4] Invoke should find the method with correct number of parameters - #32412
Closed
viirya wants to merge 1 commit into
Closed
[SPARK-35278][SQL][2.4] Invoke should find the method with correct number of parameters#32412viirya wants to merge 1 commit into
viirya wants to merge 1 commit into
Conversation
viirya
commented
May 1, 2021
MemberAuthor
SparkQA
commented
May 1, 2021
Kubernetes integration test starting |
SparkQA
commented
May 1, 2021
Kubernetes integration test status failure |
SparkQA
commented
May 1, 2021
Test build #138133 has finished for PR 32412 at commit
|
maropu
approved these changes
May 1, 2021
viirya
commented
May 1, 2021
MemberAuthor
Thanks @maropu! Merging to 2.4. |
viirya added a commit
that referenced
this pull request
May 1, 2021
…mber of parameters ### What changes were proposed in this pull request? This patch fixes `Invoke` expression when the target object has more than one method with the given method name. This is 2.4 backport of #32404. ### Why are the changes needed? `Invoke` will find out the method on the target object with given method name. If there are more than one method with the name, currently it is undeterministic which method will be used. We should add the condition of parameter number when finding the method. ### Does this PR introduce _any_ user-facing change? Yes, fixed a bug when using `Invoke` on a object where more than one method with the given method name. ### How was this patch tested? Unit test. Closes#32412 from viirya/SPARK-35278-2.4. Authored-by: Liang-Chi Hsieh <viirya@gmail.com> Signed-off-by: Liang-Chi Hsieh <viirya@gmail.com>
dongjoon-hyun
commented
May 1, 2021
Member
+1, late LGTM. Thank you all! |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 patch fixes
Invokeexpression when the target object has more than one method with the given method name. This is 2.4 backport of #32404.Why are the changes needed?
Invokewill find out the method on the target object with given method name. If there are more than one method with the name, currently it is undeterministic which method will be used. We should add the condition of parameter number when finding the method.Does this PR introduce any user-facing change?
Yes, fixed a bug when using
Invokeon a object where more than one method with the given method name.How was this patch tested?
Unit test.