godfreyhe opened a new pull request #14103: URL: https://github.com/apache/flink/pull/14103
## What is the purpose of the change *Users can't specify job name for sql job when using new apis introduced in FLIP-84. As discussion in [FLINK-18545](https://issues.apache.org/jira/browse/FLINK-18545), we should introduce `pipeline.name` in `PipelineOptions` which could work for both DataStream jobs and SQL jobs.* ## Brief change log - *Introduce `pipeline.name` to allow users to specify job name by configuration* - *Specify job name by `pipeline.name` for flink-python* - *Specify job name by `pipeline.name` for sql job* ## Verifying this change This change added tests and can be verified as follows: - *Extended StreamExecutionEnvironmentTest & PythonConfigUtilTest to verify the job name specified by pipeline.name* ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (**yes** / no) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (**yes** / no) - If yes, how is the feature documented? (not applicable / **docs** / JavaDocs / not documented) ---------------------------------------------------------------- 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: [email protected]
