[
https://issues.apache.org/jira/browse/FLINK-35744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862472#comment-17862472
]
Diljeet Singh edited comment on FLINK-35744 at 7/2/24 2:52 PM:
---------------------------------------------------------------
I do think this would be better supported via a flag on configuration of
FlinkDeployment, as it enables operator update independently from
FlinkDeployments
I am happy to make that change, Any thoughts or preferences?
was (Author: JIRAUSER306056):
I do think this would be better supported via a flag on configuration of
FlinkDeployment, as it enables operator update independently from
FlinkDeployments
I am happy to make that change and would prefer that. Any thoughts?
> Support flink 1.19 config.yaml format
> -------------------------------------
>
> Key: FLINK-35744
> URL: https://issues.apache.org/jira/browse/FLINK-35744
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Diljeet Singh
> Priority: Major
>
> Flink 1.19 introduced new
> [config.yaml|https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#flink-configuration-file]
> format. There are some
> [dependencies|https://github.com/apache/flink/blob/release-1.19.1/flink-core/src/main/java/org/apache/flink/api/common/serialization/SerializerConfigImpl.java#L378]
> on this new format in 1.19 that prevent old flink-conf.yaml from being able
> to configure properties. Since flink-kubernetes-operator and FlinkDeployments
> both rely on the flink-conf.yaml, it makes sense to be able to be able to
> configure a property to ease the transition.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
