[SPARK-47741][SQL][TESTS][FOLLOWUP] Make EXEC IMMEDIATE STACK OVERFLOW in ExecuteImmediateEndToEndSuite check the intercepted exception
#47718
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 change the test case
EXEC IMMEDIATE STACK OVERFLOWinExecuteImmediateEndToEndSuiteto check existing exception.Why are the changes needed?
Before this pr:
spark/sql/core/src/test/scala/org/apache/spark/sql/execution/ExecuteImmediateEndToEndSuite.scala
Lines 44 to 60 in e3ba74b
The test case intercepts an exception on lines 48 to 50, but the
exceptionused incheckErroris not related to the previously intercepted exception. Moreover, although the test is looped twice, the twocheckErrorcalls are actually checking the same SQL scenario, which appears to be a coding error.Does this PR introduce any user-facing change?
No, just for test
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No