You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Sean Hsuan-Yi Chu (JIRA)" <ji...@apache.org> on 2016/05/04 21:18:12 UTC
[jira] [Created] (DRILL-4656) The inferred nullability of "is null"
can at times be incorrect
Sean Hsuan-Yi Chu created DRILL-4656:
----------------------------------------
Summary: The inferred nullability of "is null" can at times be incorrect
Key: DRILL-4656
URL: https://issues.apache.org/jira/browse/DRILL-4656
Project: Apache Drill
Issue Type: Bug
Components: Query Planning & Optimization
Reporter: Sean Hsuan-Yi Chu
In SQL, the nullability of "is null" should always be non-nullable, regardless of the input type.
Because of the short-cut here [1], the nullability is true. That shortcut is to avoid the following failure in WHERE clause:
{code}
WHERE booleanFunc(ANY)
{code}
Thus, instead of terminating the logic some early, Drill should have kept going down till function resolution.
[1] https://github.com/apache/drill/blob/master/exec/java-exec/src/main/java/org/apache/drill/exec/planner/sql/TypeInferenceUtils.java#L250
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)