grundprinzip opened a new pull request, #52818:
URL: https://github.com/apache/spark/pull/52818
### What changes were proposed in this pull request?
This PR converts several IllegalArgumentException and
UnsupportedOperationException instances in the Spark Connect server to proper
SparkException with structured error classes, ensuring consistent error
propagation to clients.
Changes include:
1. Added error class definitions in error-conditions.json:
- INVALID_PARAMETER_VALUE.INTERRUPT_TYPE_TAG_REQUIRES_TAG
- INVALID_PARAMETER_VALUE.INTERRUPT_TYPE_OPERATION_ID_REQUIRES_ID
- INVALID_PARAMETER_VALUE.STREAMING_LISTENER_COMMAND_MISSING
- INVALID_ARTIFACT_PATH
- UNSUPPORTED_FEATURE.INTERRUPT_TYPE
2. Updated service handlers:
- SparkConnectInterruptHandler: Converted generic exceptions to
SparkSQLException
- SparkConnectAddArtifactsHandler: Converted to SparkRuntimeException for
invalid paths
- SparkConnectStreamingQueryListenerHandler: Converted to
SparkSQLException
3. Added test coverage in SparkConnectServiceE2ESuite
### Why are the changes needed?
Previously, the Spark Connect server threw generic Java exceptions that:
- Did not include structured error classes
- Could not be properly categorized by clients
- Provided less actionable error information
- Were inconsistent with Spark's error handling standards
The error handling infrastructure (ErrorUtils.handleError) can only
propagate error classes from SparkThrowable instances. Generic Java exceptions
are converted to generic UNKNOWN errors, losing important context.
### Does this PR introduce _any_ user-facing change?
Yes, but only to improve error messages.
Before:
java.lang.IllegalArgumentException: INTERRUPT_TYPE_TAG requested, but no
operation_tag provided.
After:
[INVALID_PARAMETER_VALUE.INTERRUPT_TYPE_TAG_REQUIRES_TAG] The value of
parameter(s)
operation_tag in interrupt is invalid: INTERRUPT_TYPE_TAG requested, but no
operation_tag provided.
Clients can now parse structured error classes for better error handling and
recovery.
### How was this patch tested?
1. Added new test cases in SparkConnectServiceE2ESuite:
- test("Interrupt with TAG type without operation_tag throws proper error
class")
- test("Interrupt with OPERATION_ID type without operation_id throws
proper error class")
2. Manual verification of error class propagation through the gRPC layer
3. All modified files pass Scala style checks
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Sonnet 4.5
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
<!--
Please clarify what changes you are proposing. The purpose of this section
is to outline the changes and how this PR fixes the issue.
If possible, please consider writing useful notes for better and faster
reviews in your PR. See the examples below.
1. If you refactor some codes with changing classes, showing the class
hierarchy will help reviewers.
2. If you fix some SQL features, you can provide some references of other
DBMSes.
3. If there is design documentation, please add the link.
4. If there is a discussion in the mailing list, please add the link.
-->
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
new features, bug fixes, or other behavior changes. Documentation-only updates
are not considered user-facing changes.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description and/or an example to show the
behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released Spark versions or within the unreleased branches such as master.
If no, write 'No'.
-->
### How was this patch tested?
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
If benchmark tests were added, please run the benchmarks in GitHub Actions
for the consistent environment, and the instructions could accord to:
https://spark.apache.org/developer-tools.html#github-workflow-benchmarks.
-->
### Was this patch authored or co-authored using generative AI tooling?
<!--
If generative AI tooling has been used in the process of authoring this
patch, please include the
phrase: 'Generated-by: ' followed by the name of the tool and its version.
If no, write 'No'.
Please refer to the [ASF Generative Tooling
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
