You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/05/19 11:57:00 UTC

[jira] [Updated] (CALCITE-7022) Decouple ModelHandler from CalciteConnection

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

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

> Decouple ModelHandler from CalciteConnection
> --------------------------------------------
>
>                 Key: CALCITE-7022
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7022
>             Project: Calcite
>          Issue Type: Task
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>
> [ModelHandler|https://github.com/apache/calcite/blob/f8fc4ca37e4a60236894c382ce8c8553adc3d43a/core/src/main/java/org/apache/calcite/model/ModelHandler.java] is mainly a parser that can transform YAML/JSON files into SchemaPlus objects.
> Currently, the class requires a CalciteConnection in order to be instantiated and the latter is a pretty heavyweight object. The usage of the CalciteConnection makes it rather cumbersome to instantiate and use the parsing capabilities of the ModelHander independently.
> In reality though, the handler does not need much from the CalciteConnection and we could easily refactor the handler to not depend on the connection at all.
> The motivation for this change is to facilitate the creation of schema objects from YAML/JSON files. A prominent use-case that I have in mind is the use of ModelHandler in unit tests where the models reside in JSON/YAML files.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)