[
https://issues.apache.org/jira/browse/CALCITE-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971265#comment-16971265
]
Danny Chen commented on CALCITE-2970:
-------------------------------------
In Flink, we also have such a expand rule to auto adapter the exchange of the
nodes, but in order to avoid the equivalence nodes explosion, we have a 2
phrase convention, one is "logica" and one is "physical". We only use this rule
in the "physical" target convention, there are still some redundant matching
for the AbstractConverters(say many AbstractConverter are wrapping another
AbstractConverter).
> Performance issue when enabling abstract converter for EnumerableConvention
> ---------------------------------------------------------------------------
>
> Key: CALCITE-2970
> URL: https://issues.apache.org/jira/browse/CALCITE-2970
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Haisheng Yuan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> If we enable the use of abstract converter for {{EnumerableConvention}}, by
> making {{useAbstractConvertersForConversion}} return true,
> {{JDBCTest.testJoinManyWay}} will not complete.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
