[
https://issues.apache.org/jira/browse/CALCITE-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007899#comment-17007899
]
Jin Xing commented on CALCITE-3285:
-----------------------------------
Hi, [~vladimirsitnikov] ~
Thanks a lot for the fix PR-1702 ~
Now I understand that the result type of *mergeJoin* is as below
{code:java}
ImmutableList.of(leftResult.physType, rightResult.physType)
{code}
And we can filter the values using predicate.
Fixing by *mergeJoin(...).where(...)* can keep the code backward compatibility
and make the code clean.
> 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)
