hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liyin Tang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-1722) The result of the test case mapjoin1.q is not correct
Date Mon, 18 Oct 2010 18:17:22 GMT

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

Liyin Tang commented on HIVE-1722:
----------------------------------

The root cause of this bug is as same as hive-1723 [https://issues.apache.org/jira/browse/HIVE-1723]
"set hive.mapjoin.cache.numrows=100" will make the test case query to use jdbm files, which
will hit the bug in hive-1723.

> The result of  the test case mapjoin1.q is not correct
> ------------------------------------------------------
>
>                 Key: HIVE-1722
>                 URL: https://issues.apache.org/jira/browse/HIVE-1722
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.6.0, 0.7.0
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>
> In the test case mapjoin1.q :
> SELECT  /*+ MAPJOIN(b) */ sum(a.key) as sum_a FROM srcpart a JOIN src b ON a.key = b.key
where a.ds is not null;
> The current result in mapjoin1.q.out shows the result is 76260.0
> But actually, if user remove the map join hint, and run the query:
> SELECT  sum(a.key) as sum_a FROM srcpart a JOIN src b ON a.key = b.key where a.ds is
not null;
> The result is 1114788.0
> And I import these input data into mysql to test, and test result is also 1114788.0.
> Obviously, the current result is not correct

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message