You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Pengcheng Xiong (JIRA)" <ji...@apache.org> on 2014/10/01 01:52:34 UTC

[jira] [Commented] (HIVE-8225) CBO trunk merge: union11 test fails due to incorrect plan

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

Pengcheng Xiong commented on HIVE-8225:
---------------------------------------

review link: https://reviews.apache.org/r/26209/

> CBO trunk merge: union11 test fails due to incorrect plan
> ---------------------------------------------------------
>
>                 Key: HIVE-8225
>                 URL: https://issues.apache.org/jira/browse/HIVE-8225
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-8225.1.patch, HIVE-8225.inprogress.patch, HIVE-8225.inprogress.patch, HIVE-8225.patch
>
>
> The result changes to as if the union didn't have count() inside. The issue can be fixed by using srcunion.value outside the subquery in count (replace count(1) with count(srcunion.value)). Otherwise, it looks like count(1) node from union-ed queries is not present in AST at all, which might cause this result.
> -Interestingly, adding group by to each query in a union produces completely weird result (count(1) is 309 for each key, whereas it should be 1 and the "logical" incorrect value if internal count is lost is 500)- Nm, that groups by table column called key, which is weird but is what Hive does



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