[ https://issues.apache.org/jira/browse/DRILL-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827221#comment-15827221 ]
Jinfeng Ni commented on DRILL-5201: ----------------------------------- You are right that Drill should not return rows where `a` value is null for query with condition a=1. Seems this is a incorrect query issue, which we probably should take a close look. Can you please provide a small sample dataset that could be used to re-produce the problem you describe? > Query bug: null values in result of a conditioned query > --------------------------------------------------------- > > Key: DRILL-5201 > URL: https://issues.apache.org/jira/browse/DRILL-5201 > Project: Apache Drill > Issue Type: Bug > Components: Client - HTTP > Affects Versions: 1.9.0 > Reporter: mehran > > I have a table with 300 columns. > When I select a query , some null columns are also returned. > This is the query that I used. > "select a,b from dfs.root.`/2016/1/17` where a=1" > For example in this query some columns are returned that "a" value is null. > I think null values are problems. Because when I add a condition to it like > "select a,b from dfs.root.`/2016/1/17` where a=1 and a IS NOT NULL" > there is not any change and still NULL values are returned. -- This message was sent by Atlassian JIRA (v6.3.4#6332)