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

Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2019/05/23 13:52:00 UTC

[jira] [Updated] (FLINK-12258) Decouple CatalogManager from Calcite

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

Aljoscha Krettek updated FLINK-12258:
-------------------------------------
    Summary: Decouple CatalogManager from Calcite  (was: Decouple CatalogManager with Calcite)

> Decouple CatalogManager from Calcite
> ------------------------------------
>
>                 Key: FLINK-12258
>                 URL: https://issues.apache.org/jira/browse/FLINK-12258
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Bowen Li
>            Assignee: Dawid Wysakowicz
>            Priority: Major
>             Fix For: 1.9.0
>
>
> FLINK-11476 introduced CatalogManager API and the FlinkCatalogManager implementation. 
> Due to that it currently depends on Calcite, a dependency that flink-table-api-java doesn't have right now. We temporarily put FlinkCatalogManager in flink-table-planner-blink.
> Idealy FlinkCatalogManager should be in flink-table-api-java module.



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