You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Pritesh Maker (JIRA)" <ji...@apache.org> on 2019/01/18 23:28:00 UTC

[jira] [Updated] (DRILL-6938) SQL get the wrong result after hashjoin and hashagg disabled

     [ https://issues.apache.org/jira/browse/DRILL-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pritesh Maker updated DRILL-6938:
---------------------------------
    Fix Version/s: 1.16.0

> SQL get the wrong result after hashjoin and hashagg disabled
> ------------------------------------------------------------
>
>                 Key: DRILL-6938
>                 URL: https://issues.apache.org/jira/browse/DRILL-6938
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.13.0
>            Reporter: Dony Dong
>            Assignee: Boaz Ben-Zvi
>            Priority: Critical
>             Fix For: 1.16.0
>
>
> Hi Team
> After we disable hashjoin and hashagg to fix out of memory issue, we got the wrong result.
> With these two parameters enabled, we will get 8 rows. After we disable them, it only return 3 rows. It seems some MEM_ID had exclude before group or some other step.
> select b.MEM_ID,count(distinct b.DEP_NO)
> from dfs.test.emp b
> where b.DEP_NO<>'-'
> and b.MEM_ID in ('68','412','852','117','657','816','135','751')
> and b.HIRE_DATE>'2014-06-01'
> group by b.MEM_ID
> order by 1;



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)