You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (JIRA)" <ji...@apache.org> on 2019/06/19 12:50:00 UTC

[jira] [Closed] (FLINK-12257) Convert CatalogTable to org.apache.calcite.schema.Table so that planner can use unified catalog APIs

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

Dawid Wysakowicz closed FLINK-12257.
------------------------------------
    Resolution: Fixed

> Convert CatalogTable to org.apache.calcite.schema.Table so that planner can use unified catalog APIs
> ----------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-12257
>                 URL: https://issues.apache.org/jira/browse/FLINK-12257
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Bowen Li
>            Assignee: Dawid Wysakowicz
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In FLINK-11476, we created CatalogManager to hook up planner with unified catalog APIs. What's missing there is, at the very last step, convert CatalogBaseTable to org.apache.calcite.schema.Table so that planner can use unified catalog APIs, like how {{ExternalTableUtil.fromExternalCatalogTable()}} works to convert the old {{ExternalCatalogTable}} to a Calcite table



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