[
https://issues.apache.org/jira/browse/CALCITE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852748#comment-16852748
]
Ruben Quesada Lopez commented on CALCITE-2973:
----------------------------------------------
Since we are going towards the deprecation of EquiJoin (CALCITE-3089), I think
it is not worth it to rush and include this ticket (and the new
EnumerablePredicativeHashJoin class) in 1.20.
Hopefully, CALCITE-3089 could be included in 1.21, which means that the new
functionality introduced by this patch will be absorbed by EnumerableHashJoin,
and we would probably have to deprecate EnumerablePredicativeHashJoin.
IMHO it is better to wait for CALCITE-3089 before moving on this one.
> Allow theta joins that have equi conditions to be executed using a hash join
> algorithm
> --------------------------------------------------------------------------------------
>
> Key: CALCITE-2973
> URL: https://issues.apache.org/jira/browse/CALCITE-2973
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.19.0
> Reporter: Lai Zhou
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.20.0
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Now the EnumerableMergeJoinRule only supports an inner and equi join.
> If users make a theta-join query for a large dataset (such as 10000*10000),
> the nested-loop join process will take dozens of time than the sort-merge
> join process .
> So if we can apply merge-join or hash-join rule for a theta join, it will
> improve the performance greatly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
