You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Atri Sharma (JIRA)" <ji...@apache.org> on 2017/07/12 18:01:00 UTC
[jira] [Commented] (CALCITE-1888) VolcanoPlanner should identify if
transformed node and original node are identical
[ https://issues.apache.org/jira/browse/CALCITE-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084414#comment-16084414 ]
Atri Sharma commented on CALCITE-1888:
--------------------------------------
Quoting [~julianhyde]:
"Is there a bug in the planner too? Maybe. Maybe it should recognize
that what you have created is IDENTICAL to what it had before, and
therefore deduce that the rule had no effect, and not cue up another
firing of the rule. That would be impressive, but I thought the
Volcano planner already did that"
We should investigate if VolcanoPlanner does the right thing, and make it do the right thing if not
> VolcanoPlanner should identify if transformed node and original node are identical
> ----------------------------------------------------------------------------------
>
> Key: CALCITE-1888
> URL: https://issues.apache.org/jira/browse/CALCITE-1888
> Project: Calcite
> Issue Type: Improvement
> Reporter: Atri Sharma
> Assignee: Julian Hyde
>
> VolcanoPlanner should identify that the transformed node and the original node are identical, hence should not fire the same rule again. This would help avoid corner cases where VolcanoPlanner gets stuck in an infinite loop
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)