[
https://issues.apache.org/jira/browse/FLINK-21570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Khachatryan resolved FLINK-21570.
---------------------------------------
Resolution: Fixed
Merged into master as
cb8a8c6925d8fbf34c64bea417606cac05e5b5d1..5b1ea1781816dd3a9b30d4438fd29436173edab6
> Add Job ID to RuntimeContext
> ----------------------------
>
> Key: FLINK-21570
> URL: https://issues.apache.org/jira/browse/FLINK-21570
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Reporter: Roman Khachatryan
> Assignee: Roman Khachatryan
> Priority: Major
> Fix For: 1.13.0
>
>
> (the issue added retroactively after the PR was merged for reference)
>
> There are some cases (e.g.
> [1|http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/How-to-get-flink-JobId-in-runtime-td36756.html],
> 2) when job ID needs to be accessed from the user code (function).
> Existing workarounds doesn't look clean (reliable).
>
> One solution discussed offline is to add {{Optional<JobID>}} to the
> {{RuntimeContext}} (the latter already contains some information of the same
> level, such as subtask index).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
