[
https://issues.apache.org/jira/browse/SPARK-26218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816087#comment-16816087
]
Marco Gaido commented on SPARK-26218:
-------------------------------------
[~rxin] I see that. But the reason for this are:
- the current behavior is against the SQL standard;
- having incorrect results in some use cases is worse than having a job
failure;
- introducing a config which allows to choose which behavior to have allows
users to decide which is the best option for their specific use cases. Moreover
I can also see people maybe having the check for overflow turned on in dev
environments, so that they can find issues and turned off in prod in order to
avoid wasting hours as you mentioned.
> 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
