[
https://issues.apache.org/jira/browse/CALCITE-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131673#comment-16131673
]
MinJi Kim commented on CALCITE-1956:
------------------------------------
I am actually curious if this was intentionally disallowed (e.g. combining
multiple full outer joins in a multi join), and if so, what the reason might
have been. Here are some small changes I made to these rules to allow full
outer joins in a multi join. Thank you for taking a look.
https://github.com/apache/calcite/pull/523
> Allow MultiJoin to contain multiple FULL joins
> ----------------------------------------------
>
> Key: CALCITE-1956
> URL: https://issues.apache.org/jira/browse/CALCITE-1956
> Project: Calcite
> Issue Type: Bug
> Reporter: MinJi Kim
> Assignee: Julian Hyde
>
> JoniToMultiJoinRule collapses multiple INNER joins into a single MultiJoin.
> I was wondering if all the joins are full outer joins, couldn't we use the
> same logic to allow MultiJoins to contains multiple FULL joins? This would
> allow LoptOptimizeJoinRule to re-order full outer joins, just like inner
> joins.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
