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

Max Gekk commented on SPARK-42838:
----------------------------------

[~breakpointsca] The ticket will be assigned to you when we merge your PR. No 
need to assign it in advance, please, have a look at the rules for contributors 
(https://spark.apache.org/contributing.html):

9. The related JIRA, if any, will be marked as “In Progress” and your pull 
request will automatically be linked to it. There is no need to be the Assignee 
of the JIRA to work on it, though you are welcome to comment that you have 
begun work.

> Assign a name to the error class _LEGACY_ERROR_TEMP_2000
> --------------------------------------------------------
>
>                 Key: SPARK-42838
>                 URL: https://issues.apache.org/jira/browse/SPARK-42838
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 3.5.0
>            Reporter: Max Gekk
>            Priority: Minor
>              Labels: starter
>
> Choose a proper name for the error class *_LEGACY_ERROR_TEMP_2000* defined in 
> {*}core/src/main/resources/error/error-classes.json{*}. The name should be 
> short but complete (look at the example in error-classes.json).
> Add a test which triggers the error from user code if such test still doesn't 
> exist. Check exception fields by using {*}checkError(){*}. The last function 
> checks valuable error fields only, and avoids dependencies from error text 
> message. In this way, tech editors can modify error format in 
> error-classes.json, and don't worry of Spark's internal tests. Migrate other 
> tests that might trigger the error onto checkError().
> If you cannot reproduce the error from user space (using SQL query), replace 
> the error by an internal error, see {*}SparkException.internalError(){*}.
> Improve the error message format in error-classes.json if the current is not 
> clear. Propose a solution to users how to avoid and fix such kind of errors.
> Please, look at the PR below as examples:
>  * [https://github.com/apache/spark/pull/38685]
>  * [https://github.com/apache/spark/pull/38656]
>  * [https://github.com/apache/spark/pull/38490]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to