[
https://issues.apache.org/jira/browse/FLINK-33643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weihua Hu resolved FLINK-33643.
-------------------------------
Fix Version/s: 1.19.0
Resolution: Fixed
resolved in master: 220287539854c8f32f9d85541026f2b018bd5ef3
> Allow StreamExecutionEnvironment's executeAsync API to use default JobName
> --------------------------------------------------------------------------
>
> Key: FLINK-33643
> URL: https://issues.apache.org/jira/browse/FLINK-33643
> Project: Flink
> Issue Type: Improvement
> Components: Client / Job Submission
> Affects Versions: 1.19.0
> Reporter: Matt Wang
> Assignee: Matt Wang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> On the `execute` API of StreamExecutionEnvironment, jobName is allowed to be
> Null. In this case, the default jobName in StreamGraphGenerator
> (`DEFAULT_STREAMING_JOB_NAME` or `DEFAULT_BATCH_JOB_NAME`) will be used, but
> the logic of `executeAsync` does not allow jobName to be Null. I think the
> processing logic should be unified here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
