hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-20292) Bad join ordering in tpcds query93 with primary constraint defined
Date Sat, 04 Aug 2018 09:28:00 GMT


Hive QA commented on HIVE-20292:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
was found in seen patch url's cache and a test was probably run already on it. Aborting...

This message is automatically generated.

ATTACHMENT ID: 12934377 - PreCommit-HIVE-Build

> Bad join ordering in tpcds query93 with primary constraint defined
> ------------------------------------------------------------------
>                 Key: HIVE-20292
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Planning
>            Reporter: Vineet Garg
>            Assignee: Vineet Garg
>            Priority: Major
>         Attachments: HIVE-20292.1.patch, HIVE-20292.2.patch, HIVE-20292.3.patch, HIVE-20292.4.patch,
> Query 93 has join (including outer) b/w store_sales, store_return and reason.  Without
constraints store_return is joined with reason and then with store_sales.
> But if a primary key is added on store_return (alter table store_returns add constraint
tpcds_pk_sr primary key (sr_item_sk, sr_ticket_number) disable novalidate rely) join order
becomes ((store_sales, store_return), reason) which is very inefficient.

This message was sent by Atlassian JIRA

View raw message