You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@calcite.apache.org by "Hongze Zhang (JIRA)" <ji...@apache.org> on 2019/05/27 09:30:00 UTC

[jira] [Created] (CALCITE-3093) Decouple JDBC connection calls from PlannerImpl

Hongze Zhang created CALCITE-3093:
-------------------------------------

             Summary: Decouple JDBC connection calls from PlannerImpl
                 Key: CALCITE-3093
                 URL: https://issues.apache.org/jira/browse/CALCITE-3093
             Project: Calcite
          Issue Type: Improvement
          Components: core
            Reporter: Hongze Zhang
            Assignee: Hongze Zhang


Currently the class {{PlannerImpl}} creates JDBC connections[1] internally to instantiate {{RelOptPlanner}}. For improving the design I suggest to reverse the call chain, for example, we can make JDBC API call PlannerImpl to create {{RelOptPlanner}}, {{SqlValidator}}, {{SqlToRelConverter}} instances, etc.

This JIRA topic is the first step of the improvement - we should decouple the use of JDBC API from PlannerImpl. Planner API is designed to be a reusable toolkit and we should make it work individually without the help of JDBC API.

[1] https://github.com/apache/calcite/blob/4e1b68e3c0b2a90832cc790c6166cebb14ae2970/core/src/main/java/org/apache/calcite/prepare/PlannerImpl.java#L143-L151



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)