[
https://issues.apache.org/jira/browse/HIVE-12700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyong Zhu updated HIVE-12700:
--------------------------------
Attachment: job explain plan.txt
Implicit Joins.hql
explicit join key.hql
> complex join keys cannot be recognized in Hive 0.13
> ---------------------------------------------------
>
> Key: HIVE-12700
> URL: https://issues.apache.org/jira/browse/HIVE-12700
> Project: Hive
> Issue Type: Bug
> Components: Logical Optimizer
> Affects Versions: 0.13.1
> Reporter: Xiaoyong Zhu
> Priority: Critical
> Attachments: Implicit Joins.hql, explicit join key.hql, job explain
> plan.txt
>
>
> Hi Experts
> I am using Hive 0.13 and find a potential bug. Attached “implicit join.hql”
> has several join keys (for example store_sales.ss_addr_sk =
> customer_address.ca_address_sk) and cannot be regonized by Hive. In such
> cases hive won’t be able to optimize and can only do a cross join first which
> makes the job runs really long. If I change the log to explicit join keys,
> then it works well.
> For the below simple query hive can regcogonize the join keys, and I think
> Hive should be able to handle the complex situations such as my example,
> right?
>
> SELECT *
> FROM table1 t1, table2 t2, table3 t3
> WHERE t1.id = t2.id AND t2.id = t3.id AND t1.zipcode = '02535';
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
