[
https://issues.apache.org/jira/browse/CALCITE-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031700#comment-17031700
]
Ruben Q L commented on CALCITE-3285:
------------------------------------
[~vladimirsitnikov], I understand your point.
But even when / if MergeJoin provides an efficient implementation of conditions
like {{a.id > b.id-10 and a.id<b.id+10}}, I think there might be
non-optimizable clauses in the condition that would need to be handled via a
Predicate, e. g. {{a.id > b.id-10 and a.id<b.id+10 and MY_FUNCTION(a.name) <>
MY_FUNCTION(b.name)}}
> 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: Vladimir Sitnikov
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h
> 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)
