[
https://issues.apache.org/jira/browse/FLINK-21570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306143#comment-17306143
]
Chesnay Schepler edited comment on FLINK-21570 at 3/22/21, 11:57 AM:
---------------------------------------------------------------------
Because technically you cannot add methods to {{@Public}} interfaces; it would
break all implementations.
Adding PublicEvolving does that too, but it also effectively results in this
addition being ignored. (the alternative being an explicit ignore in our
japicmp configuration)
was (Author: zentol):
Because technically you cannot add methods to {{@Public}} interfaces; it would
break all implementation.
Adding PublicEvolving does that too, but it also effectively results in this
addition being ignored. (the alternative being an explicit ignore in our
japicmp configuration)
> 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
> Labels: pull-request-available
> 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)
