[jira] [Commented] (DRILL-5237) Same query produces different/wrong results

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848268#comment-15848268 ] 

ASF GitHub Bot commented on DRILL-5237:
---------------------------------------

GitHub user Serhii-Harnyk opened a pull request:

    https://github.com/apache/drill/pull/735

    DRILL-5237: Same query produces different/wrong results

    Fixed loss of nested fields from the schema when the first FlattenRecordBatch is empty

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Serhii-Harnyk/drill DRILL-5237

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/735.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #735
    
----
commit 800953b7ec924ea31ffc21327950c84528f3c492
Author: Serhii-Harnyk <se...@gmail.com>
Date:   2017-01-27T15:36:10Z

    DRILL-5237: Same query produces different/wrong results

----


> Same query produces different/wrong results
> -------------------------------------------
>
>                 Key: DRILL-5237
>                 URL: https://issues.apache.org/jira/browse/DRILL-5237
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Serhii Harnyk
>            Assignee: Serhii Harnyk
>         Attachments: test_data.tar.gz
>
>
> Query 
> {code:sql}
> select count(*) as col from (select t1.a.a1 from (select t.*, flatten(t.b) as b from dfs.`/tmp/test_data` t where t.c is not null) t1 where t1.a .a1 like 'a1');
> {code}
> returns different results for different values for option planner.width.max_per_node
> With options 
> {code:sql}
> alter session set `planner.slice_target` = 1;
> alter session set `planner.width.max_per_node` = 1;
> {code}
> query returns correct result:
> {noformat}
> +------+
> | col  |
> +------+
> | 3    |
> +------+
> {noformat}
> but with options 
> {code:sql}
> alter session set `planner.slice_target` = 1;
> alter session set `planner.width.max_per_node` = 3;
> {code}
> the same query returns wrong result 
> {noformat}
> +------+
> | col  |
> +------+
> | 2    |
> +------+
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)