You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2016/12/12 17:51:58 UTC

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

Julian Hyde created CALCITE-1536:
------------------------------------

             Summary: 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.4#6332)