[
https://issues.apache.org/jira/browse/FLINK-28648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039410#comment-18039410
]
Gyula Fora commented on FLINK-28648:
------------------------------------
We decided back then that the change in behaviour was the desired default
behaviour. I would like to avoid changing this (since this feature was released
already) unless there is a good argument why this new behaviour should not be
the default going forward. I understand that it's a change in behaviour but
during upgrade you can easily set a different default config in your platform.
> Allow session deletion to block on any running job
> --------------------------------------------------
>
> Key: FLINK-28648
> URL: https://issues.apache.org/jira/browse/FLINK-28648
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Nishita Pattanayak
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.13.0
>
>
> Currently session FlinkDeployment deletion blocks on existing
> FlinkSessionJob-s for that cluster.
> We could add the option to block on any running job in case it is an
> unmanaged job deployed through the Flink CLI directly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
