[
https://issues.apache.org/jira/browse/FLINK-11546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051191#comment-17051191
]
Kostas Kloudas commented on FLINK-11546:
----------------------------------------
I think that in some context, static {{JobId}}s are desirable (e.g. Standalone
per-job mode) but there are some scenarios where we may give users a way to
shoot theirselves on the foot.
For example, how do we handle the case when we have 2 jobs submitted with the
same {{jobId}} on a running session cluster? We fail the submission or we
re-submit with a random {{JobId}}?
Given this, I am not against adding this feature but we need to be careful on
the scope.
> Add option to manually set job ID in CLI
> ----------------------------------------
>
> Key: FLINK-11546
> URL: https://issues.apache.org/jira/browse/FLINK-11546
> Project: Flink
> Issue Type: Sub-task
> Components: Command Line Client
> Affects Versions: 1.7.0
> Reporter: Ufuk Celebi
> Assignee: vinoyang
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Add an option to specify the job ID during job submissions via the CLI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
