[ https://issues.apache.org/jira/browse/FLINK-26075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marios Trivyzas reassigned FLINK-26075: --------------------------------------- Assignee: Marios Trivyzas > Persist per-ExecNode configuration > ---------------------------------- > > Key: FLINK-26075 > URL: https://issues.apache.org/jira/browse/FLINK-26075 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / Planner > Reporter: Timo Walther > Assignee: Marios Trivyzas > Priority: Major > > Even though a compiled plan is static, some configuration options still > change the topology of an ExecNode. In general, we will request users to keep > the configuration constant between Flink versions. However, setting > configuration more fine-grained per-ExecNode is a frequently requested > feature. It can also allow us to set the parallelism more fine-grained in the > future. > We need the following infrastructure for the mentioned use cases: > - Every ExecNode can have a configuration > - By default the configuration per node are the values from the global > configuration using the keys from the ExecNodeMetadata annotation. > - We persist the ExecNode configuration in the JSON plan. > - If the persisted plan contains a configuration, the persisted configuration > is merged with the global configuration and has priority. -- This message was sent by Atlassian Jira (v8.20.1#820001)