[
https://issues.apache.org/jira/browse/CALCITE-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010004#comment-17010004
]
Julian Hyde commented on CALCITE-3285:
--------------------------------------
{quote}The sad thing is there's no clear way to prevent creating
EnumerableMergeJoin without non-equi join conditions.
{quote}
There is a mechanism. The constructor of the RelNode can throw
InvalidRelException. EnumerableAggregate does this, for instance, when given a
distinct aggregate function.
Let's not over-use this mechanism, but it is a way for particular RelNode
sub-classes to say 'I can't handle 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: 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)
