[
https://issues.apache.org/jira/browse/CALCITE-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006383#comment-17006383
]
Vladimir Sitnikov commented on CALCITE-3285:
--------------------------------------------
[[email protected]], [~hyuan] it looks like MergeJoin implementation is not
symmetrical.
In other words, the resultset depends on the order of the inputs.
For instance, org.apache.calcite.runtime.EnumerablesTest#testMergeJoin4. If I
swap join inputs, then the join suddenly produces 2 rows instead of 4.
I have not verified which one is better, but merge join should be symmetrical.
Can you please check that?
> EnumerableMergeJoin should support non-equi join conditions
> -----------------------------------------------------------
>
> Key: CALCITE-3285
> URL: https://issues.apache.org/jira/browse/CALCITE-3285
> Project: Calcite
> Issue Type: Improvement
> Reporter: Haisheng Yuan
> Assignee: Jin Xing
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.22.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Calcite should be able to generate EnumerableMergeJoin with non-equi join
> conditions, as long as there are equi-join conditions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
