Paul Rogers created DRILL-6358:
----------------------------------
Summary: Null value returned from WHERE a IS NOT NULL query
Key: DRILL-6358
URL: https://issues.apache.org/jira/browse/DRILL-6358
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.13.0
Reporter: Paul Rogers
Consider the following input file:
{noformat}
{a: null}
{a: 10}
{noformat}
Then run the following. The result is as expected:
{noformat}
SELECT * FROM `json/null-int.json` WHERE a IS NOT NULL;
+-----+
| a |
+-----+
| 10 |
+-----+
{noformat}
Now, do something similar. Create a file that repeats the first record 70,000
times. Call it {{70Knulls.json}}. Run the same query. The results are bizarre:
{noformat}
SELECT * FROM `gen/70Knulls.json` WHERE a IS NOT NULL;
+-------+
| ** |
+-------+
| null |
+-------+
{noformat}
The column name of "\*\*" I probably due to DRILL-6357. The query may be
treating a as a missing column, and fill in the bogus "\*\*" field.
So, there is no column {{a}} in that theory. So, no rows should have matched.
But, then. column {{a}} finally appeared. Why does it have a null value, not
10? And, why did the null value pass the {{IS NOT NULL}} test?
Anyway, expected the same output as the two-line case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)