[
https://issues.apache.org/jira/browse/CALCITE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807826#comment-16807826
]
Stamatis Zampetakis commented on CALCITE-2973:
----------------------------------------------
Thanks for working on this [~hhlai1990] ! It seems that it is not only a rule
issue but you also plan to change the merge join algorithm implementation. I
think the summary is a bit misleading. How about changing it to "Allow theta
joins to be executed using a merge join algorithm" or something similar?
Apart from that, I think it would be better to generalize EnumerableMergeJoin
operator than create a new one.
> Make EnumerableMergeJoinRule to support a theta join
> ----------------------------------------------------
>
> 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
>
> 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)
