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

Use "Planner" to handle query preparation process in CalcitePrepareImpl

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None
    • 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

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            julianhyde Julian Hyde

            Dates

              Created:
              Updated:

              Slack

                Issue deployment