Details
-
Umbrella
-
Status: In Progress
-
Major
-
Resolution: Unresolved
-
3.3.0
-
None
Description
The PR https://github.com/apache/spark/pull/32850 introduced error classes as a part of the error messages framework (https://issues.apache.org/jira/browse/SPARK-33539). Need to migrate all exceptions from QueryExecutionErrors, QueryCompilationErrors and QueryParsingErrors on the error classes using instances of SparkThrowable, and carefully test every error class by writing tests in dedicated test suites:
- QueryExecutionErrorsSuite for the errors that are occurred during query execution
- QueryCompilationErrorsSuite ... query compilation or eagerly executing commands
- QueryParsingErrorsSuite ... parsing errors
Here is an example https://github.com/apache/spark/pull/35157 of how an existing Java exception can be replaced, and testing of related error classes.At the end, we should migrate all exceptions from the files Query.*Errors.scala and cover all error classes from the error-classes.json file by tests.
Attachments
Issue Links
- is blocked by
-
SPARK-34920 Introduce SQLSTATE and ERRORCODE to SQL Exception
-
- Resolved
-
-
SPARK-33539 Standardize exception messages in Spark
-
- Open
-
- is related to
-
SPARK-41288 Server-specific improvement, error handling and API
-
- Open
-
- links to