[
https://issues.apache.org/jira/browse/CALCITE-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248795#comment-17248795
]
Jinpeng Wu commented on CALCITE-4432:
-------------------------------------
Hi, Julian. I think the top-down rule driver may be a general solution for this
problem:
# Transformation rules that lead to set merging are generally fired before
implementations rules
# During implemetation/optimization phase, optimization will stop directly
when cycles are detected. So cyclic nodes should have no chance to become the
best of its RelSubset.
> When the RelNode's input is the same subset as the node belonged to, not
> choose this node as best.
> --------------------------------------------------------------------------------------------------
>
> Key: CALCITE-4432
> URL: https://issues.apache.org/jira/browse/CALCITE-4432
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Ziwei Liu
> Assignee: Ziwei Liu
> Priority: Major
>
> If a subset have a cyclic node, the node's input is this subset itself. If
> the beset
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
