You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Takeshi Yamamuro (Jira)" <ji...@apache.org> on 2019/10/27 00:37:00 UTC
[jira] [Resolved] (SPARK-28512) New optional mode: throw runtime
exceptions on casting failures
[ https://issues.apache.org/jira/browse/SPARK-28512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Takeshi Yamamuro resolved SPARK-28512.
--------------------------------------
Fix Version/s: 3.0.0
Assignee: Gengliang Wang
Resolution: Fixed
Resolved by [https://github.com/apache/spark/pull/25997]
> New optional mode: throw runtime exceptions on casting failures
> ---------------------------------------------------------------
>
> Key: SPARK-28512
> URL: https://issues.apache.org/jira/browse/SPARK-28512
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Gengliang Wang
> Assignee: Gengliang Wang
> Priority: Major
> Fix For: 3.0.0
>
>
> In popular DBMS like MySQL/PostgreSQL/Oracle, runtime exceptions are thrown on casting, e.g. cast('abc' as boolean)
> While in Spark, the result is converted as null silently. It is by design since we don't want a long-running job aborted by some casting failure. But there are scenarios that users want to make sure all the data conversion are correct, like the way they use MySQL/PostgreSQL/Oracle.
> This one has a bigger scope than https://issues.apache.org/jira/browse/SPARK-28741
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org