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

Use "Planner" to handle query preparation process in CalcitePrepareImpl

    XMLWordPrintableJSON

    Details

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

      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 Merlino:

      Compare and contrast:

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated: