[
https://issues.apache.org/jira/browse/CALCITE-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944334#comment-16944334
]
Stamatis Zampetakis commented on CALCITE-2970:
----------------------------------------------
I'm with you [~hyuan], that was exactly my point. I asked for a profiling just
to verify that there is not something obvious that we can do. Apart from that
another way to mitigate the problem would be to restrict the scope of rules
(especially for rules matching logical and physical operators) and/or organize
the rule application in phases.
> Performance issue when enabling abstract converter for EnumerableConvertion
> ---------------------------------------------------------------------------
>
> 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)
