[ 
https://issues.apache.org/jira/browse/FLINK-29313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605779#comment-17605779
 ] 

Matyas Orhidi commented on FLINK-29313:
---------------------------------------

The short term fix could be to do an upgrade when these properties are changed 
in the spec.flinkConfiguration. (This was the original behaviour in 1.1.0.) 
I'll try to come up with a good solution before going down this path.

> Some config overrides are ignored when set under spec.flinkConfiguration
> ------------------------------------------------------------------------
>
>                 Key: FLINK-29313
>                 URL: https://issues.apache.org/jira/browse/FLINK-29313
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.2.0
>            Reporter: Matyas Orhidi
>            Priority: Blocker
>             Fix For: kubernetes-operator-1.2.0
>
>
> Some 
> [configs|https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/configuration/#resourceuser-configuration]
>  that can be specified under spec.flinkConfiguration won't take affect 
> without an upgrade, e.g.:
>  * {{kubernetes.operator.periodic.savepoint.interval}}
>  * {{kubernetes.operator.savepoint.format.type}}
> These properties are used mainly from the so called 'observeConfig', and 
> won't be available in the operator until the job is restarted. Ideally these 
> should be changed without an upgrade, but at the moment they won't take 
> affect at all.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to