hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8225) CBO trunk merge: union11 test fails due to incorrect plan
Date Mon, 06 Oct 2014 23:19:33 GMT

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

Hive QA commented on HIVE-8225:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12673134/HIVE-8225.5.patch

{color:green}SUCCESS:{color} +1 6525 tests passed

Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1134/testReport
Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1134/console
Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1134/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12673134

> 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
>            Priority: Critical
>             Fix For: 0.14.0
>
>         Attachments: HIVE-8225.1.patch, HIVE-8225.2.patch, HIVE-8225.3.patch, HIVE-8225.4.patch,
HIVE-8225.5.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)

Mime
View raw message