[
https://issues.apache.org/jira/browse/FLINK-12348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833738#comment-16833738
]
Timo Walther commented on FLINK-12348:
--------------------------------------
Yes, we should only have a single location for those properties. And a
string-string map should be used for interoperability with YAML, JSON etc.
However, we should provide some methods for setting frequently used properties
with nice Javadocs in the string-string map. Setting and getting a timezone is
a good example.
> 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)
