You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/07/01 09:51:00 UTC

[jira] [Created] (FLINK-28349) Consider using resource uid as fixed jobid for operator deployed jobs

Gyula Fora created FLINK-28349:
----------------------------------

             Summary: Consider using resource uid as fixed jobid for operator deployed jobs
                 Key: FLINK-28349
                 URL: https://issues.apache.org/jira/browse/FLINK-28349
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
            Reporter: Gyula Fora


There are certain connectors that rely on jobid uniqueness to a certain degree (such as the iceberg sink connector) so it might make sense to use the FlinkDeployment uid as the fixed job id instead of the default 0000000000000000.

cc [~matyas] [~wangyang0918] 

If we decide to do so we have to be mindful of the migration path for already running jobs with HA/last-state upgrade mode.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)