[
https://issues.apache.org/jira/browse/FLINK-16835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068873#comment-17068873
]
Seth Wiesman commented on FLINK-16835:
--------------------------------------
My intuition from a user perspective of how I would expect this to work.
flink-conf.yaml < TableEnvironment < Query
flink-conf.yaml to allow setting cluster-wide defaults for all config options.
TableEnvironment to allow setting deployment wide defaults.
Query level which equates to a single flink job although this might be out of
scope for this ticket.
I would find it surprising if the StreamExecutionEnvironment affected
table-specific configurations.
> Replace TableConfig with Configuration
> --------------------------------------
>
> Key: FLINK-16835
> URL: https://issues.apache.org/jira/browse/FLINK-16835
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Timo Walther
> Priority: Major
>
> In order to allow reading and writing of configuration from a file or
> string-based properties. We should consider removing {{TableConfig}} and
> fully rely on a Configuration-based object with {{ConfigOptions}}.
> This effort was partially already started which is why
> {{TableConfig.getConfiguration}} exists.
> However, we should clarify if we would like to have control and traceability
> over layered configurations such as {{flink-conf,yaml <
> StreamExecutionEnvironment < TableEnvironment}}. Maybe the {{Configuration}}
> class is not the right abstraction for this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
