[
https://issues.apache.org/jira/browse/HIVE-20744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677134#comment-16677134
]
Hive QA commented on HIVE-20744:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12947013/HIVE-20744.04.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/14772/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/14772/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-14772/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12947013/HIVE-20744.04.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12947013 - PreCommit-HIVE-Build
> Use SQL constraints to improve join reordering algorithm
> --------------------------------------------------------
>
> Key: HIVE-20744
> URL: https://issues.apache.org/jira/browse/HIVE-20744
> Project: Hive
> Issue Type: Bug
> Components: CBO
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Major
> Attachments: HIVE-20744.01.patch, HIVE-20744.02.patch,
> HIVE-20744.03.patch, HIVE-20744.04.patch, HIVE-20744.patch
>
>
> Till now, it was all based on stats stored for the base tables and their
> columns. Now the optimizer can rely on constraints. Hence, this patch is for
> the join reordering costing to use constraints, and if it does not find any,
> rely on old code path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
