[
https://issues.apache.org/jira/browse/CALCITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856746#comment-16856746
]
Stamatis Zampetakis commented on CALCITE-3111:
----------------------------------------------
I didn't have in mind physical nodes but rather logical ones that are not
necessarily our in-house logical operators. It may also be relevant for
physical operators in the sense that we never pass through a logical plan. For
instance, we could configure {{SqlToRelConverter}} with a {{RelBuilder}} that
generates directly physical operators. I guess the latter cannot work if
{{RelDecorrelator}} is bound to our Logical nodes.
> Allow custom implementations of Correlate in RelDecorrelator
> ------------------------------------------------------------
>
> Key: CALCITE-3111
> URL: https://issues.apache.org/jira/browse/CALCITE-3111
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Juhwan Kim
> Assignee: Juhwan Kim
> Priority: Minor
>
> Currently, RelDecorrelator code only works for LogicalCorrelate.
> Decorrelating through Calcite would become much more flexible if it allows
> using custom implementations of Correlate. This would require refactoring all
> logical rels used in RelDecorrelator to the abstract ones(e.g
> LogicalCorrelate -> Correlate).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
