You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2020/03/27 16:35:00 UTC
[jira] [Updated] (FLINK-16835) Replace TableConfig with
Configuration
[ https://issues.apache.org/jira/browse/FLINK-16835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther updated FLINK-16835:
---------------------------------
Description:
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.
was:
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 {{ConfigOption}}s.
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.
> 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)