You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Uroš Bojanić (Jira)" <ji...@apache.org> on 2026/10/12 08:52:00 UTC
[jira] [Comment Edited] (SPARK-43253) Assign a name to the error class _LEGACY_ERROR_TEMP_2017
[ https://issues.apache.org/jira/browse/SPARK-43253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126240#comment-18126240 ]
Uroš Bojanić edited comment on SPARK-43253 at 10/12/26 8:51 AM:
----------------------------------------------------------------
[~deepujain] converted this to internal error, which seems like the correct way forward here. cc [~maxgekk]
was (Author: JIRAUSER313574):
@deepujain converted this to internal error, which seems like the correct way forward here. cc [~maxgekk]
> Assign a name to the error class _LEGACY_ERROR_TEMP_2017
> --------------------------------------------------------
>
> Key: SPARK-43253
> URL: https://issues.apache.org/jira/browse/SPARK-43253
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.5.0
> Reporter: Max Gekk
> Assignee: Deepak Jain (DJ)
> Priority: Minor
> Labels: pull-request-available, starter
> Fix For: 4.4.0
>
>
> Choose a proper name for the error class *_LEGACY_ERROR_TEMP_2017* 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org