[
https://issues.apache.org/jira/browse/SPARK-60187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18126253#comment-18126253
]
Devansh Singh commented on SPARK-60187:
---------------------------------------
I am working on this issue.
> Assign a name to the error condition _LEGACY_ERROR_TEMP_1000
> ------------------------------------------------------------
>
> Key: SPARK-60187
> URL: https://issues.apache.org/jira/browse/SPARK-60187
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 5.0.0
> Reporter: Devansh Singh
> Priority: Minor
>
> Choose a proper name for the error condition _LEGACY_ERROR_TEMP_1000 defined
> in common/utils/src/main/resources/error/error-conditions.json. The name
> should be short but complete (look at the example in error-conditions.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-conditions.json
> without worrying about 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-conditions.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: [email protected]
For additional commands, e-mail: [email protected]
