hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20292) Bad join ordering in tpcds query93 with primary constraint defined
Date Mon, 06 Aug 2018 15:30:00 GMT

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

Ashutosh Chauhan commented on HIVE-20292:
-----------------------------------------

+1
Lets also revisit sub_count_check in a follow-up.

> Bad join ordering in tpcds query93 with primary constraint defined
> ------------------------------------------------------------------
>
>                 Key: HIVE-20292
>                 URL: https://issues.apache.org/jira/browse/HIVE-20292
>             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,
HIVE-20292.5.patch, HIVE-20292.6.patch, HIVE-20292.7.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
(v7.6.3#76005)

Mime
View raw message