[
https://issues.apache.org/jira/browse/SPARK-49011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Milicevic resolved SPARK-49011.
-------------------------------------
Resolution: Fixed
Resolved with: https://github.com/apache/spark/pull/47553
> [M0] Improve exceptions thrown from parser/interpreter
> ------------------------------------------------------
>
> Key: SPARK-49011
> URL: https://issues.apache.org/jira/browse/SPARK-49011
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 4.0.0
> Reporter: David Milicevic
> Priority: Major
>
> With SPARK-48350 we have introduced exception condition and states for
> exceptions thrown internally from SQL Scripting parser or interpreter.
> However, these errors are throwing SparkException, which isn't completely
> suitable for scripting because with it we need to parametrize each exception
> to output the line where the error occurred. Example in:
> [https://github.com/apache/spark/pull/47404.]
> We want to introduce a class for exceptions that will have Origin as a
> parameter, and then each message can automatically have prepended info about
> the line on which the exception occurred.
>
> Introduction of Error class for SQL Scripting:
> [https://github.com/apache/spark/pull/47147]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
