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 2021/07/26 10:36:00 UTC

[jira] [Created] (FLINK-23498) Use a layered configuration in Executor and Planner

Timo Walther created FLINK-23498:
------------------------------------

             Summary: 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


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.configure}} to propagate changes to the {{StreamExecutionEnvironment}} layer
- {{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)