[
https://issues.apache.org/jira/browse/FLINK-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142631#comment-15142631
]
Ufuk Celebi commented on FLINK-3299:
------------------------------------
I think you raise valid points. But as long as we don't have these figured it
out yet, I would like to be defensive and not have it as part of the 1.0
release. Currently, the only usage is in the DB state backend and there we can
get rid of it. After figuring it out, we can easily add such an ID back.
> Remove ApplicationID from Environment
> -------------------------------------
>
> Key: FLINK-3299
> URL: https://issues.apache.org/jira/browse/FLINK-3299
> Project: Flink
> Issue Type: Improvement
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> Fix For: 1.0.0
>
>
> {{ApplicationID}} is used to identify an application across many job
> submissions (for example after restoring from a savepoint). This is currently
> exposed in the {{Environment}}, which might be unnecessary.
> State backends, which need the ID can generate it themselves and store it as
> part of their state handle.
> This has to be checked with the DB state backend, which currently uses this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
