[CALCITE-1525] Use "Planner" to handle query preparation process in CalcitePrepareImpl

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Julian Hyde
• Created: 02/Dec/16 20:16
• Updated: 20/Aug/20 14:27

Description

The query preparation process (parse, validate, convert SqlNode to RelNode, plan) is complicated, and each step depends on state on the previous one. We have two ways of managing that preparation process: CalcitePrepareImpl (used by the JDBC driver) and org.apache.calcite.tools.Planner (your only practical option if your code doesn't live inside JDBC).

We should make CalcitePrepareImpl use a Planner internally, get rid of shared logic, and make them behave consistently.

From email thread with gian:

Compare and contrast:

• CalcitePrepareImpl.getSqlToRelConverter
• PlannerImpl.rel

Issue Links

• depends upon: CALCITE-1536 Initialize cluster before planner
• is related to: CALCITE-4179 org.apache.calcite.jdbc package polluting core Calcite planning packages
• relates to: CALCITE-1509 Allow overriding the convertlet table in CalcitePrepareImpl