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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CALCITE-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated CALCITE-3093:
------------------------------------
    Labels: pull-request-available  (was: )

> 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
>            Priority: Major
>              Labels: pull-request-available
>
> 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)