[
https://issues.apache.org/jira/browse/FLINK-26297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-26297.
--------------------------------
Fix Version/s: 1.15.0
Resolution: Fixed
Fixed in master:
commit 56da73a457a9c9150db90d58627bf2c8a08ebf7c
[table-planner] Rename PlannerConfiguration to PlannerConfig
commit e2b743c98d2aabfa028c0cc79a54b62ad30507da
[table] Use `tableConfig` as name for `TableConfig` variables
commit 1b67cd0f1583847f2d784e06f05e8f0dbb06fbee
[table-planner][table-runtime] Introduce ExecNodeConfig
commit bd46985d1ddfea02b398a744f0521094a019b487
[table-planner] Rename ShortcutUtils method to get TableConfig
> 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
> Fix For: 1.15.0
>
>
> 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)
