[
https://issues.apache.org/jira/browse/FLINK-28648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039406#comment-18039406
]
Mark Nuttall commented on FLINK-28648:
--------------------------------------
Hello ... I know this has been out for nearly four months now, but was it the
intent to introduce a breaking behaviour change under this issue? In
[https://github.com/apache/flink-kubernetes-operator/pull/994] the author
asserts that there were no changes in the public API - which would be true if
in KubernetesOperatorConfigOptions, we had \{{ .defaultValue(false) }} - but
that's not what happened. Would anyone object to a small PR that changed the
default behaviour so that users had to opt in to this new feature, rather than
opt out as is currently the case? [~gyfora] [~nishita0905] many thanks in
advance for your thoughts.
> 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)
