[SPARK-39899][SQL] Fix passing of message parameters to InvalidUDFClassException
#37323
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?
In the PR, I propose to pass
messageParameters
toAnalysisException
fromInvalidUDFClassException
.Also, I propose to replace
checkErrorClass
bycheckError
in the test "NO_HANDLER_FOR_UDAF: No handler for UDAF error" to check that the message parameters are passed correctly, and make the test independent from the message of the error classNO_HANDLER_FOR_UDAF
.Why are the changes needed?
To fix a bug and provide actual message parameters to users.
Does this PR introduce any user-facing change?
Yes. After the changes, users receive non-empty message parameters.
How was this patch tested?
By running the modified test suite: