[
https://issues.apache.org/jira/browse/HIVE-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623009#comment-13623009
]
Hudson commented on HIVE-3464:
------------------------------
Integrated in Hive-trunk-hadoop2 #138 (See
[https://builds.apache.org/job/Hive-trunk-hadoop2/138/])
HIVE-3464 : Merging join tree may reorder joins which could be invalid
(Navis via Ashutosh Chauhan) (Revision 1464230)
Result = FAILURE
hashutosh :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464230
Files :
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/ErrorMsg.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java
* /hive/trunk/ql/src/test/queries/clientpositive/mergejoins_mixed.q
* /hive/trunk/ql/src/test/queries/clientpositive/smb_mapjoin_17.q
* /hive/trunk/ql/src/test/results/clientpositive/join_filters_overlap.q.out
* /hive/trunk/ql/src/test/results/clientpositive/mergejoins_mixed.q.out
* /hive/trunk/ql/src/test/results/clientpositive/smb_mapjoin_17.q.out
> Merging join tree may reorder joins which could be invalid
> ----------------------------------------------------------
>
> Key: HIVE-3464
> URL: https://issues.apache.org/jira/browse/HIVE-3464
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.10.0
> Reporter: Navis
> Assignee: Navis
> Fix For: 0.11.0
>
> Attachments: HIVE-3464.D5409.2.patch, HIVE-3464.D5409.3.patch,
> HIVE-3464.D5409.4.patch, HIVE-3464.D5409.5.patch, HIVE-3464.D5409.6.patch
>
>
> Currently, hive merges join tree from right to left regardless of join types,
> which may introduce join reordering. For example,
> select * from a join a b on a.key=b.key join a c on b.key=c.key join a d on
> a.key=d.key;
> Hive tries to merge join tree in a-d=b-d, a-d=a-b, b-c=a-b order and a-d=a-b
> and b-c=a-b will be merged. Final join tree is "a-(bdc)".
> With this, ab-d join will be executed prior to ab-c. But if join type of -c
> and -d is different, this is not valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
