[
https://issues.apache.org/jira/browse/ASTERIXDB-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694166#comment-17694166
]
ASF subversion and git services commented on ASTERIXDB-3113:
------------------------------------------------------------
Commit d8e460e25cf578e5d3dd837e77188b56f75648c1 in asterixdb's branch
refs/heads/master from Wail Alkowaileet
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=d8e460e25c ]
[ASTERIXDB-3113] Allow using hash-join with redundant variables
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
This patch introduces several optimizations:
- Remove redundant equality checks in join conditions
- Allow one attribute to be joined with two attributes
using hash-join
Change-Id: I3226457e4c9352fae0433cfeb39a158ec6562955
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17377
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Wail Alkowaileet <[email protected]>
Reviewed-by: Ali Alsuliman <[email protected]>
> Allow the use hash-join with redundant variables
> ------------------------------------------------
>
> Key: ASTERIXDB-3113
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3113
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: COMP - Compiler
> Reporter: Wail Y. Alkowaileet
> Assignee: Wail Y. Alkowaileet
> Priority: Major
>
> The following join currently uses broadcast join instead of hash-joinÂ
> {code:java}
> SELECT COUNT(*)
> FROM Orders o, LineItem l
> WHERE o.o_orderkey = l.l_orderkey
> AND o.o_orderkey = l.l_suppkey{code}
> As a result of having one attribute on one side and two attributes on the
> other side. The broadcast join would be much slower in most cases. Hence,
> this should be rectified.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
