You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/11/20 03:35:40 UTC
[GitHub] [flink] wuchong commented on pull request #14103: [FLINK-18545] Introduce `pipeline.name` to allow users to specify job name by configuration
wuchong commented on pull request #14103:
URL: https://github.com/apache/flink/pull/14103#issuecomment-730823946
Hi @kl0u , I don't think the job name configuration conflicts with application mode. I think multi-execute applications may al so have same job name, e.g. use the default job name when submitting using `env.execute()`.
With the job name configuration, users can still change the job name before submitting, for example:
```java
Configuration conf = new Configuration();
conf.setString("pipeline.name", "job1");
env.configure(conf, Thread.currentThread().getContextClassLoader);
env.execute(); // submit job1
conf.setString("pipeline.name", "job2");
env.configure(conf, Thread.currentThread().getContextClassLoader);
env.execute(); // submit job2
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org