Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-1536

Initialize cluster before planner

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                julianhyde Julian Hyde
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated: