[jira] [Comment Edited] (CALCITE-1536) Initialize cluster before planner

["Julian Hyde (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005442#comment-16005442 ] 

Julian Hyde edited comment on CALCITE-1536 at 5/10/17 9:16 PM:
---------------------------------------------------------------

Some issues related to CALCITE-1536:
* CALCITE-473 would like to be able to enable and disable particular rules within a Program;
* CALCITE-1774 would like to be able to add (and enable) new rules once planning has begun.


was (Author: julianhyde):
Some issues related to CALCITE-1536:
* CALCITE-473 would like to be able to enable and disable particular rules within a Program;
* CALCITE-1474 would like to be able to add (and enable) new rules once planning has begun.

> Initialize cluster before planner
> ---------------------------------
>
>                 Key: CALCITE-1536
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1536
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>
> We should initialize the cluster ({{RelOptCluster}}) before planner ({{RelOptPlanner}}, or a sub-class such as {{VolcanoPlanner}} or {{HepPlanner}}). Currently the planner contains important information such as executor ({{RelOptPlanner.Executor}}), the set of active traits (epitomized by the {{RelOptPlanner.emptyTraitSet}} method) and the metadata providers, and the cluster contains a link to a planner, so the planner has to be created first.
> This makes it difficult to use a succession of planners for query planning. Fixing this issue is a first step towards CALCITE-1525.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)