[
https://issues.apache.org/jira/browse/CALCITE-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056845#comment-17056845
]
Stamatis Zampetakis commented on CALCITE-3285:
----------------------------------------------
Everybody in this discussion seem to agree that the merge join should support
non-equi join conditions, if the condition contains at least one equality
conjunction.
I had a quick look in [PR#1788|https://github.com/apache/calcite/pull/1788] and
it seems that it can achieve this purpose without any significant overhead for
the case of equi-joins thus I think it is a good step forwards.
[~vladimirsitnikov] raised some concerns regarding the usefulness of the new
API in EnumerableDefaults. In order to move forward, I would suggest to mark
this API as experimental and if in the near future somebody has a better idea
of how to tackle this problem we can easily remove it.
How do people feel about this?
> 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)
