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

Posted to issues@flink.apache.org by "Bowen Li (JIRA)" <ji...@apache.org> on 2019/01/31 19:48:00 UTC

[jira] [Closed] (FLINK-10768) Move external catalog related code from TableEnvironment to CatalogManager

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

Bowen Li closed FLINK-10768.
----------------------------
    Resolution: Duplicate

> Move external catalog related code from TableEnvironment to CatalogManager
> --------------------------------------------------------------------------
>
>                 Key: FLINK-10768
>                 URL: https://issues.apache.org/jira/browse/FLINK-10768
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API &amp; SQL
>            Reporter: Bowen Li
>            Assignee: Bowen Li
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Add a new CatalogManager class and port existing Calcite-directly-related code from TableEnvironment into CatalogManager.
> Background: there are two parallel efforts going on right now - FLINK-10686, driven by Timo, includes moving external catalogs APIs from flink-table to flink-table-common, also from Scala to Java; FLINK-10744 I'm working on right now to integrate Flink with Hive and enhance external catalog functionality.
> As discussed with @twalthr in FLINK-10689, we'd better parallelize these efforts while introducing minimal overhead for integrating them later. Our agreed way is to writing new code/feature related to external catalogs/hive in Java in flink-table first then move to other module like flink-table-common, this way we can minimize migration efforts. If existing classes are modified for a feature we can start migrating them to Java in a separate commit first and then perform the actual feature changes, and migrated classes can be placed in flink-table/src/main/java until we find a better module structure.
> Thus, this is NOT a feature, but purely refactor, thus no new functions should be introduced. It acts the pre-requisite for FLINK-10698



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