[jira] [Commented] (HIVE-8558) CBO: enable n-way joins after CBO join reordering

["Hive QA (JIRA)" <ji...@apache.org>]

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

Hive QA commented on HIVE-8558:
-------------------------------



{color:red}Overall{color}: -1 at least one tests failed

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

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 6573 tests executed
*Failed tests:*
{noformat}
org.apache.hive.minikdc.TestJdbcWithMiniKdc.testNegativeTokenAuth
{noformat}

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12676276 - PreCommit-HIVE-TRUNK-Build

> CBO: enable n-way joins after CBO join reordering
> -------------------------------------------------
>
>                 Key: HIVE-8558
>                 URL: https://issues.apache.org/jira/browse/HIVE-8558
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Harish Butani
>            Assignee: Harish Butani
>         Attachments: HIVE-8558.1.patch
>
>
> With CBO, we disable n-way joins.  But for consecutive tables we can safely collapse into n-way joins. For e.g this is safe to collapse:
> {code}
> select p1.p_name, p2.p_name, p3.p_name from part p1 join part p2 on p1.p_name = p2.p_name join part p3 on p3.p_name = p1.p_name;
> {code}
> whereas, we shouldn't reorder in this case:
> {code}
> select p1.p_name, p2.p_name, p3.p_name 
> from part p1 join part p2 on p1.p_name = p2.p_name join part p3 on p3.p_size = p1.p_size and p3.p_size = p2.p_size join part p4 on p1.p_name = p4.p_name;
> {code}



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