[
https://issues.apache.org/jira/browse/FLINK-23498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-23498.
--------------------------------
Fix Version/s: 1.14.0
Resolution: Fixed
Fixed in 1.14.0:
commit 779070274cf00cb475cb7bab1332317ba39ac16e
[table] Introduce a full planner configuration
commit d19d044c125d31fa6392d746d8c707857ae8dc47
[table-planner] Remove unused field from PlannerBase
commit 5b2535bb5a23833a7e4115061f10ab17a7979fc4
[streaming-java] Expose an easier StreamExecutionEnvironment.configure()
commit bf554282567749966ab7d2e5b894de71f7436813
[streaming-java] Expose StreamExecutionEnvironment.getConfiguration()
commit 659ffa78d1b0dfe39ec8dac5b04cfc0c29f57fc3
[streaming-java] Remove StreamExecutionEnvironment.getConfiguration()
> Use a layered configuration in Executor and Planner
> ---------------------------------------------------
>
> Key: FLINK-23498
> URL: https://issues.apache.org/jira/browse/FLINK-23498
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataStream, Table SQL / API
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> The configuration story in Flink is not very consistent at the moment.
> Ideally, we should have a layered approach where pipeline executor,
> DataStream API, and Table API store their configuration and add it to a
> global configuration on request. However, this is a big change that we would
> like to avoid at this point.
> Instead, we partially follow this approach by adding:
> - {{Executor.getConfiguration}} to access the config of lower layers
> - {{Planner.getConfiguration}} to access a global configuration during
> planning
> This is required to access properties stored in
> {{StreamExecutionEnvironment.configuration}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
