[SPARK-50338][CORE] Make LazyTry exceptions less verbose #48882
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?
For LazyTry, we want two stack traces:
The first one is added as suppressed exception. The second one is stitched into the stack trace of the rethrown exception.
The third one (
TRY_WITH_CALLER_STACKTRACE_TRY_STACKTRACE
) doesn't need to be visible to users as a suppressed exception. We only need the depth of the stacktrace untildoTryWithCallerStacktrace
. Use a custom exceptionOriginalTryStackTraceException
to store it together with the suppressed first one.Why are the changes needed?
The suppressed Exception was too verbose.
Does this PR introduce any user-facing change?
Yes. Stacktraces of Exceptions coming from a LazyTry (e.g. QueryExecution plans) should be more readable.
How was this patch tested?
Unit tests were adapted.
Was this patch authored or co-authored using generative AI tooling?
No.