[CALCITE-1536] Initialize cluster before planner

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Julian Hyde
• Created: 12/Dec/16 17:51
• Updated: 28/Nov/22 08:16

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.

Issue Links

• is depended upon by: CALCITE-1525 Use "Planner" to handle query preparation process in CalcitePrepareImpl
• is related to: CALCITE-405 Combine RelOptCluster, RelOptQuery into RelOptPlanner
• is related to: CALCITE-5401 Rule fired by HepPlanner can return Volcano's RelSubset
• is related to: CALCITE-473 Create a wrapper Program to support the ability to enable/disable rules
• is related to: CALCITE-1499 Exclude VolcanoPlanner's "originalRoot" from default planning process
• relates to: CALCITE-1774 Allow rules to be registered during planning process
• relates to: CALCITE-1653 Pass an expression executor to RexUtil.simplify for constant reduction
• relates to: CALCITE-1996 Executing RelBuilder.values with a projection sometimes fails
• relates to: CALCITE-1681 Provide a way to copy RelNode trees between clusters