You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2022/04/24 08:46:00 UTC
[jira] [Closed] (FLINK-27360) Rename clusterId field of FlinkSessionJobSpec to deploymentName
[ https://issues.apache.org/jira/browse/FLINK-27360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yang Wang closed FLINK-27360.
-----------------------------
Resolution: Fixed
Fixed via:
main: 4559495fc554595c03f4569fa5fd52ff214967e3
> Rename clusterId field of FlinkSessionJobSpec to deploymentName
> ---------------------------------------------------------------
>
> Key: FLINK-27360
> URL: https://issues.apache.org/jira/browse/FLINK-27360
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Aitozi
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.0.0
>
>
> Since the sessionjob logic only works together with a FlinkDeployment, and the clusterId always has to match the name, it would be better to explicitly call it deploymentName so that it is more intuitive for the users.
> What do you think?
> cc [~aitozi]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)