You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Parth Chandra (JIRA)" <ji...@apache.org> on 2015/04/07 06:53:12 UTC
[jira] [Updated] (DRILL-2349) null comparison behavior difference
between drill and postgres
[ https://issues.apache.org/jira/browse/DRILL-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Parth Chandra updated DRILL-2349:
---------------------------------
Fix Version/s: (was: 0.9.0)
1.0.0
> null comparison behavior difference between drill and postgres
> --------------------------------------------------------------
>
> Key: DRILL-2349
> URL: https://issues.apache.org/jira/browse/DRILL-2349
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Data Types
> Reporter: Chun Chang
> Assignee: Parth Chandra
> Priority: Critical
> Fix For: 1.0.0
>
>
> It appears postgres returns null for the following comparison:
> {code}
> foodmart=# select null=1;
> ?column?
> ----------
> (1 row)
> foodmart=# select null <> 1;
> ?column?
> ----------
> (1 row)
> foodmart=# select null;
> ?column?
> ----------
> (1 row)
> {code}
> Drill gives sqlValidatorException:
> {code}
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> select null=1 from sys.drillbits;
> Query failed: SqlValidatorException: Cannot apply '=' to arguments of type '<NULL> = <INTEGER>'. Supported form(s): '<COMPARABLE_TYPE> = <COMPARABLE_TYPE>'
> Error: exception while executing query: Failure while executing query. (state=,code=0)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)