[
https://issues.apache.org/jira/browse/ASTERIXDB-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17948308#comment-17948308
]
ASF subversion and git services commented on ASTERIXDB-3573:
------------------------------------------------------------
Commit a3676425d89570b2c9c83b81cac8c2f67105acec in asterixdb's branch
refs/heads/master from Ali Alsuliman
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=a3676425d8 ]
Revert "[ASTERIXDB-3573][COMP] Do not pull predicates out of join condition"
This reverts commit a08dd5bfce1bd82c49d2f1240e94484825de862c.
Reason for revert: performance regression in some queries with complex join
condition (e.g. CH2 Q19).
Ext-ref: MB-65642
Change-Id: I9036a302d30c65f4596ff2a6d2ea6d16a8af3921
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19703
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Ali Alsuliman <[email protected]>
Reviewed-by: Murtadha Hubail <[email protected]>
> Do not pull predicates out of join condition
> --------------------------------------------
>
> Key: ASTERIXDB-3573
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3573
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: COMP - Compiler
> Reporter: Ali Alsuliman
> Assignee: Ali Alsuliman
> Priority: Major
> Labels: triaged
>
> Avoid pulling predicates out of the (inner) join condition into a separate
> select operator.
> https://issues.apache.org/jira/browse/ASTERIXDB-3572 takes care of
> non-equality predicates and employs a hash-join as long as there is at least
> one equality predicate. With that being done, there is now no need to pull
> non-equality predicates out of the (inner) join condition. These predicates
> can still be present in the join condition together with the other equality
> predicates. This can reduce the cardinality of the join operator and improve
> performance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
