[
https://issues.apache.org/jira/browse/FLINK-12348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833212#comment-16833212
]
Jark Wu commented on FLINK-12348:
---------------------------------
Hi [~twalthr], I find that the updates to TableConfig mentioned in FLIP-32 is
mainly for a builder pattern. But the most important change Blink introduced is
making TableConfig configurable using plain key-value pairs (similar to runtime
options in {{flink-conf.yaml}}). So that we can setup a cluster or a job using
yaml files, for example:
{code:java}
sql.timeZone: UTC
sql.codegen.length.max: 64000
{code}
In order to support this feature, we need a member
{{org.apache.flink.configuration.Configuration}} in {{TableConfig}}. And move
{{TableConfigOptions}} into api module. What do you think? [~twalthr]
[~hequn8128] [~dawidwys]
> 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)
