[
https://issues.apache.org/jira/browse/FLINK-8844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202053#comment-17202053
]
Matthias commented on FLINK-8844:
---------------------------------
This issue was visited as part of the Backlog grooming of the Engine team on
Sep 25, 2020:
There is a workaround to achieve that by using the global job parameters. One
could parse the `META-INF/MANIFEST.MF` to extract the relevant version
information and pass it into the configuration as `GlobalJobParameters`.
This issue is still valid, though.
> Export job jar file name or job version property via REST API
> -------------------------------------------------------------
>
> Key: FLINK-8844
> URL: https://issues.apache.org/jira/browse/FLINK-8844
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Affects Versions: 1.4.3
> Reporter: Elias Levy
> Priority: Major
>
> To aid automated deployment of jobs, it would be useful if the REST API
> exposed either a running job's jar filename or a version property the job
> could set, similar to how it sets the job name.
> As it is now there is no standard mechanism to determine what version of a
> job is running in a cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
