[
https://issues.apache.org/jira/browse/FLINK-27095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518145#comment-17518145
]
Usamah Jassat commented on FLINK-27095:
---------------------------------------
I understand that the two clusters are very different but what if the user
changed their mind about the type of cluster they wanted?
E.g. if a user were to accidentally create an Application Cluster and then
realize they actually wanted a Session Cluster, currently they can't change it
without deleting the FlinkDeployment then creating a new one.
Or is this the kind of behaviour we want?
> Allow FlinkDeployment Mode Switching
> ------------------------------------
>
> Key: FLINK-27095
> URL: https://issues.apache.org/jira/browse/FLINK-27095
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Usamah Jassat
> Priority: Major
> Fix For: kubernetes-operator-1.0.0
>
>
> Currently the operator doesn't allow switching the mode of an existing
> FlinkDeployment between Application and Session.
> I don't see why this shouldn't be allowed, if the mode is switched we should
> tear-down the cluster and spin-up a new cluster running in this new mode. It
> will add complexity into the connector but seems like a valid use-case.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
