[
https://issues.apache.org/jira/browse/CALCITE-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009405#comment-17009405
]
Vladimir Sitnikov commented on CALCITE-3285:
--------------------------------------------
The sad thing is there's no clear way to prevent creating EnumerableMergeJoin
without non-equi join conditions.
In other words, even if EnumerableMergeJoinRule would create just trivial joins
that has only equi conditions, other rules (FilterJoinRule) might push filters
into the join converting it into non-equi join.
So either we need a way to tell if a join instance supports non-equi conditions
(or if it supports outer joins), or we need to implement that through extra
filter at the Enumerablerel#implement phase.
> 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)
