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

Posted to issues@flink.apache.org by "Jing Zhang (JIRA)" <ji...@apache.org> on 2019/04/28 03:05:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16827800#comment-16827800 ] 

Jing Zhang commented on FLINK-12348:
------------------------------------

IMO, `TableConfigOptions` should also exist in API module, although TableConfigOptions now only works for Blink table planner and Blink table runtime.  [~jark] What do you think?

> 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 / API
>            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
(v7.6.3#76005)