hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-9112) Query may generate different results depending on the number of reducers
Date Tue, 06 Jan 2015 20:24:34 GMT

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

Chao commented on HIVE-9112:
----------------------------

Forgot to mention, the plan from last comment is for the last query in {{subquery_in}}:

{code}
-- non agg, corr, with join in Parent Query
select p.p_partkey, li.l_suppkey
from (select distinct l_partkey as p_partkey from lineitem) p join lineitem li on p.p_partkey
= li.l_partkey
where li.l_linenumber = 1 and
 li.l_orderkey in (select l_orderkey from lineitem where l_shipmode = 'AIR' and l_linenumber
= li.l_linenumber)
;
{code}

> Query may generate different results depending on the number of reducers
> ------------------------------------------------------------------------
>
>                 Key: HIVE-9112
>                 URL: https://issues.apache.org/jira/browse/HIVE-9112
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Chao
>            Assignee: Chao
>
> Some queries may generate different results depending on the number of reducers, for
example, tests like ppd_multi_insert.q, join_nullsafe.q, subquery_in.q, etc.
> Take subquery_in.q as example, if we add
> {noformat}
> set mapred.reduce.tasks=3;
> {noformat}
> to this test file, the result will be different (and wrong):
> {noformat}
> @@ -903,5 +903,3 @@ where li.l_linenumber = 1 and
>  POSTHOOK: type: QUERY
>  POSTHOOK: Input: default@lineitem
>  #### A masked pattern was here ####
> -108570 8571
> -4297   1798
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message