You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/04/15 19:50:25 UTC
[jira] [Closed] (FLINK-3759) Table API should throw exception is
null value is encountered in non-null mode.
[ https://issues.apache.org/jira/browse/FLINK-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabian Hueske closed FLINK-3759.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
Fixed with 722155a1fb95ddb45b6ee4c6cc6d0438cdbafac6
> Table API should throw exception is null value is encountered in non-null mode.
> -------------------------------------------------------------------------------
>
> Key: FLINK-3759
> URL: https://issues.apache.org/jira/browse/FLINK-3759
> Project: Flink
> Issue Type: Bug
> Components: Table API
> Affects Versions: 1.1.0
> Reporter: Fabian Hueske
> Priority: Critical
> Fix For: 1.1.0
>
>
> The Table API can be configured to omit null-checks in generated code to speed up processing. Currently, the generated code replaces a null value with a data type specific default value if it is encountered in non-null-check mode.
> This can silently cause wrong results and should be changed such that an exception is thrown if a null value is encountered in non-null-check mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)