[SPARK-53857] Enable messageTemplate propagation to SparkThrowable #52559
+237
−8
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
|
Adding @cloud-fan, @dejankrak-db, @yuchenhuo, @davidm-db |
cloud-fan
reviewed
Oct 10, 2025
cloud-fan
reviewed
Oct 10, 2025
sql/api/src/main/scala/org/apache/spark/sql/AnalysisException.scala
Outdated
Show resolved
Hide resolved
|
We need to fix the binary compatibility issuse detected by mima. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 pull request enhances Spark error handling capabilities, primarily within
AnalysisException, to support more flexible and maintainable error message rendering.Why are the changes needed?
The goal is to add a new default method,
getDefaultMessageTemplate, to the publicSparkThrowableinterface. This gives clients a consistent, machine-readable default template for error rendering, while leaving them free to localize or otherwise transform the message.This approach helps create a single source of truth for error definitions.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Unit tests and existing tests.
Was this patch authored or co-authored using generative AI tooling?
No