[
https://issues.apache.org/jira/browse/SPARK-26218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814709#comment-16814709
]
Reynold Xin commented on SPARK-26218:
-------------------------------------
The no-exception is by design. Imagine you have an ETL job that runs for hours,
and then it suddenly throws an exception because one row overflows ...
> Throw exception on overflow for integers
> ----------------------------------------
>
> Key: SPARK-26218
> URL: https://issues.apache.org/jira/browse/SPARK-26218
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Marco Gaido
> Priority: Major
>
> SPARK-24598 just updated the documentation in order to state that our
> addition is a Java style one and not a SQL style. But in order to follow the
> SQL standard we should instead throw an exception if an overflow occurs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
