You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Boaz Ben-Zvi (Jira)" <ji...@apache.org> on 2019/11/05 04:04:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16967220#comment-16967220 ]
Boaz Ben-Zvi commented on DRILL-6938:
-------------------------------------
[~dony.dong] - can this case be closed ? Looks like it only affected 1.13 ....
> 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
>
> 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
(v8.3.4#803005)