You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Chun Chang (JIRA)" <ji...@apache.org> on 2015/02/28 04:16:04 UTC
[jira] [Created] (DRILL-2349) null comparison behavior difference
between drill and postgres
Chun Chang created DRILL-2349:
---------------------------------
Summary: 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: Daniel Barclay (Drill)
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)