[jira] [Commented] (SPARK-37935) Migrate onto error classes

["Apache Spark (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-37935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521024#comment-17521024 ] 

Apache Spark commented on SPARK-37935:
--------------------------------------

User 'panbingkun' has created a pull request for this issue:
https://github.com/apache/spark/pull/36160

> Migrate onto error classes
> --------------------------
>
>                 Key: SPARK-37935
>                 URL: https://issues.apache.org/jira/browse/SPARK-37935
>             Project: Spark
>          Issue Type: Umbrella
>          Components: Spark Core, SQL
>    Affects Versions: 3.3.0
>            Reporter: Max Gekk
>            Assignee: Max Gekk
>            Priority: Major
>
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org