[
https://issues.apache.org/jira/browse/HIVE-20576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619040#comment-16619040
]
Zoltan Haindrich commented on HIVE-20576:
-----------------------------------------
the plan looks right; toggling vectorization doesn't change the plan - but it
causes incorrect results to appear
{code}
--! qt:dataset:src
set hive.transpose.aggr.join=true;
set hive.vectorized.execution.enabled=true;
set hive.auto.convert.join=true;
set hive.auto.convert.join.noconditionaltask.size=10000000;
-- HIVE-5891 Alias conflict when merging multiple mapjoin tasks into their
common
-- child mapred task
EXPLAIN
SELECT x.key FROM (
SELECT c.key FROM
(SELECT a.key FROM src a JOIN src b ON a.key=b.key GROUP BY a.key) tmp
JOIN src c ON tmp.key=c.key
UNION ALL
SELECT c.key FROM
(SELECT a.key FROM src a JOIN src b ON a.key=b.key GROUP BY a.key) tmp
JOIN src c ON tmp.key=c.key
) x order by x.key;
SELECT x.key FROM (
SELECT c.key FROM
(SELECT a.key FROM src a JOIN src b ON a.key=b.key GROUP BY a.key) tmp
JOIN src c ON tmp.key=c.key
UNION ALL
SELECT c.key FROM
(SELECT a.key FROM src a JOIN src b ON a.key=b.key GROUP BY a.key) tmp
JOIN src c ON tmp.key=c.key
) x order by x.key;
{code}
> Fix incorrect results in multiMapJoin2 when hive.transpose.aggr.join is
> enabled
> -------------------------------------------------------------------------------
>
> Key: HIVE-20576
> URL: https://issues.apache.org/jira/browse/HIVE-20576
> Project: Hive
> Issue Type: Bug
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
>
> there are a lot of empty rows appearing in one of the result sets; and a lot
> of real values going away...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
