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

Posted to issues@flink.apache.org by "godfrey he (Jira)" <ji...@apache.org> on 2019/09/27 05:21:00 UTC

[jira] [Closed] (FLINK-12348) Use TableConfig in API module to replace TableConfig in blink-planner-module

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

godfrey he closed FLINK-12348.
------------------------------

Fixed in 1.9.0: 428c7049882cfc482562b69d1a367cdb9b0eec72

> Use TableConfig in API module to replace TableConfig in blink-planner-module
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-12348
>                 URL: https://issues.apache.org/jira/browse/FLINK-12348
>             Project: Flink
>          Issue Type: Task
>          Components: Table SQL / Planner
>            Reporter: Jing Zhang
>            Assignee: Jing Zhang
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Since TableConfig already moved to API module in [FLINK-11067|https://issues.apache.org/jira/browse/FLINK-11067], TableConfig in blink-planner-module should not exist anymore. The issue aims to remove the TableConfig in blink-planner-module, use TableConfig in API module instead.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)