You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Khalid Mammadov (Jira)" <ji...@apache.org> on 2022/10/10 21:30:00 UTC

[jira] [Commented] (SPARK-37945) Use error classes in the execution errors of arithmetic ops

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

Khalid Mammadov commented on SPARK-37945:
-----------------------------------------

[~maxgekk] I see you have already fixed most of these, I can pick up (and started already) below ones if Ok? 

unscaledValueTooLargeForPrecisionError
decimalPrecisionExceedsMaxPrecisionError
outOfDecimalTypeRangeError
integerOverflowError

Ps: Looks fearly streightforward and shouldn't take long

> Use error classes in the execution errors of arithmetic ops
> -----------------------------------------------------------
>
>                 Key: SPARK-37945
>                 URL: https://issues.apache.org/jira/browse/SPARK-37945
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 3.3.0
>            Reporter: Max Gekk
>            Priority: Major
>
> Migrate the following errors in QueryExecutionErrors:
> * overflowInSumOfDecimalError
> * overflowInIntegralDivideError
> * arithmeticOverflowError
> * unaryMinusCauseOverflowError
> * binaryArithmeticCauseOverflowError
> * unscaledValueTooLargeForPrecisionError
> * decimalPrecisionExceedsMaxPrecisionError
> * outOfDecimalTypeRangeError
> * integerOverflowError
> onto use error classes. Throw an implementation of SparkThrowable. Also write a test per every error in QueryExecutionErrorsSuite.



--
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