[
https://issues.apache.org/jira/browse/FLINK-32589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742840#comment-17742840
]
Gyula Fora commented on FLINK-32589:
------------------------------------
I think this is not necessarily something that should be handled on the
operator side otherwise the user has no way of actually removing the overrides.
If they use kubectly apply (serversideApply) without the override config
defined, the configs would be naturally merged and carried over. By replacing
the user can remove it by not setting the override.
> Carry over parallelism overrides to prevent users from clearing them on
> updates
> -------------------------------------------------------------------------------
>
> Key: FLINK-32589
> URL: https://issues.apache.org/jira/browse/FLINK-32589
> Project: Flink
> Issue Type: Improvement
> Components: Autoscaler, Kubernetes Operator
> Reporter: Maximilian Michels
> Priority: Major
>
> The autoscaler currently sets the parallelism overrides via the Flink config
> {{pipeline.jobvertex-parallelism-overrides}}. Whenever the user posts specs
> updates, special care needs to be taken in order to carry over existing
> overrides. Otherwise the job will reset to the default parallelism
> configuration. Users shouldn't have to deal with this. Instead, whenever a
> new spec is posted which does not contain the overrides, the operator should
> automatically apply the last-used overrides (if autoscaling is enabled).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
