[
https://issues.apache.org/jira/browse/FLINK-26075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther closed FLINK-26075.
--------------------------------
Fix Version/s: 1.15.0
Resolution: Fixed
Fixed in master:
commit 84723eea4e7ddae846092ca8bb0905a7b9d6dc6a
[table-planner][test] Regenerate JSON plans
commit bc11450bbf2519924e354af7900174e7bd6c33e3
[table-planner] Persist node configuration to JSON plan
Fixed in 1.15:
commit ec8e43d584054d3b9dc7783a4646f51cd81bcc10
[table-planner][test] Regenerate JSON plans
commit 00c1439bc3cc277fc37e39d084c4f1bc14ecf5b7
[table-planner] Persist node configuration to JSON plan
> 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
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> 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)
