[
https://issues.apache.org/jira/browse/CALCITE-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381994#comment-14381994
]
Ng Jiunn Jye commented on CALCITE-631:
--------------------------------------
I agree with you on processing based on JdbcJoin.condition. And I totally
missed out the reverse left right in my previous patch. Thanks for pointing
them out.
[CALCITE-631]JdbcJoinToSupportNonEquiJoin.2.patch is new patch which converting
condition RexCall into SqlJoin. The previous patch is no longer relevant.
As the condition has all the information, the new patch is able to work on
combination joins using of AND and OR. I have added test case in
JdbcAdapterTest to test this as well.
I am a bit confused with your explanation on Common theta cases. Can you
provide some reference link ?
Thank you.
> JdbcJoin to support Non-EquiJoin
> --------------------------------
>
> Key: CALCITE-631
> URL: https://issues.apache.org/jira/browse/CALCITE-631
> Project: Calcite
> Issue Type: Improvement
> Reporter: Ng Jiunn Jye
> Assignee: Julian Hyde
> Fix For: next
>
> Attachments: [CALCITE-631]JdbcJoinToSupportNonEquiJoin.2.patch,
> [CALCITE-631]JdbcJoinToSupportNonEquiJoin.patch
>
>
> Currently, the JdbcJoin only support EquiJoin. ie select * from tab1 inner
> join tab2 on tab1.col1=tab2.col2
> NonEqui join are not supported in JdbcJoin, thus resulting execution plan
> which uses EnumerationJoin and EnumerableCalc for joining and not pushing the
> join down to remote database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
