You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Vineet Garg (JIRA)" <ji...@apache.org> on 2018/08/01 23:49:00 UTC

[jira] [Created] (HIVE-20292) Bad join ordering in query93 with primary constraint defined

Vineet Garg created HIVE-20292:
----------------------------------

             Summary: Bad join ordering in 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


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)