Julian Hyde commented on CALCITE-1934:

Would CALCITE-1536 solve this problem? You would create two VolcanoPlanner 
instances, but all of the necessary state could be re-used.

I think your fix will be fine short-term until CALCITE-1536 is fixed, then we'd 
remove re-entrancy. And in fact VolcanoPlanner would become immutable. 

> Make VolcanoPlanner reentrant
> -----------------------------
>                 Key: CALCITE-1934
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1934
>             Project: Calcite
>          Issue Type: New Feature
>            Reporter: Ted Xu
>            Assignee: Julian Hyde
> VolcanoPlanner should be reentrant so as to do an additional round of 
> optimize (possibly with different set of rules) without recompile RelNodes.

This message was sent by Atlassian JIRA

Reply via email to