[
https://issues.apache.org/jira/browse/ASTERIXDB-3572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944604#comment-17944604
]
ASF subversion and git services commented on ASTERIXDB-3572:
------------------------------------------------------------
Commit 59ace80151c0c8039645cf191af060163aea13d2 in asterixdb's branch
refs/heads/master from Ali Alsuliman
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=59ace80151 ]
[ASTERIXDB-3572][COMP] Use hash-join when condition contains equi predicate
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
When the join condition contains at least one equality
predicate, a hash-join can be used instead of nested loop join.
Ext-ref: MB-65612
Change-Id: I5ca76afb607c725beaf68272e917d0566000a6ac
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19473
Integration-Tests: Jenkins <[email protected]>
Tested-by: Ali Alsuliman <[email protected]>
Reviewed-by: Ali Alsuliman <[email protected]>
Reviewed-by: Peeyush Gupta <[email protected]>
> Hash-join not used when join condition has other non-equality predicates
> ------------------------------------------------------------------------
>
> Key: ASTERIXDB-3572
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3572
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: COMP - Compiler
> Reporter: Ali Alsuliman
> Assignee: Ali Alsuliman
> Priority: Major
> Labels: triaged
>
> Currently, when the join condition of a LEFT OUTER JOIN has non-equality
> predicates, nested loop join algorithm is chosen. However, a hash-join can be
> used when there is at least one equality predicate:
>
> {code:java}
> SELECT ds1, ds2
> FROM ds1 LEFT JOIN ds2 ON ds1.st > ds2.st AND ds1.st < ds2.et AND ds1.x =
> ds2.x;{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)