[
https://issues.apache.org/jira/browse/FLINK-26297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther updated FLINK-26297:
---------------------------------
Description:
Introduce ExecutionNodeConfig to be used instead of planner.getConfiguration()
and planner.getTableConfig(), as a first step, to facilitate a merged
configuration, combining
the persisted configuration of the ExecNodes with the one coming from the
environment.
This is also a prerequisite to solve various issues with configuration that is
not propagated from flink-conf.yaml all the way down to operators.
was:
Introduce ExecutionNodeConfig to be used instead of planner.getConfiguration()
and planner.getTableConfig(), as a first step, to facilitate a merged
configuration, combining
the persisted configuration of the ExecNodes with the one coming from the
environment.
> Introduce ExecutionNodeConfig which will be used in all Exec Nodes
> ------------------------------------------------------------------
>
> Key: FLINK-26297
> URL: https://issues.apache.org/jira/browse/FLINK-26297
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Marios Trivyzas
> Assignee: Marios Trivyzas
> Priority: Major
> Labels: pull-request-available
>
> Introduce ExecutionNodeConfig to be used instead of planner.getConfiguration()
> and planner.getTableConfig(), as a first step, to facilitate a merged
> configuration, combining
> the persisted configuration of the ExecNodes with the one coming from the
> environment.
> This is also a prerequisite to solve various issues with configuration that
> is not propagated from flink-conf.yaml all the way down to operators.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
