Max Gekk created SPARK-37935:
--------------------------------
Summary: Migrate onto error classes
Key: SPARK-37935
URL: https://issues.apache.org/jira/browse/SPARK-37935
Project: Spark
Issue Type: Umbrella
Components: SQL
Affects Versions: 3.3.0
Reporter: Max Gekk
Assignee: Max Gekk
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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
