[
https://issues.apache.org/jira/browse/FLINK-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148558#comment-15148558
]
ASF GitHub Bot commented on FLINK-3299:
---------------------------------------
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/1642
[FLINK-3299] Remove ApplicationID from Environment
As per discussion in the issue, we decided to remove the the
`ApplicationID`.
Replaces the app ID in RocksDB and DB backend with job ID. I've talked to
@gyfora about the DB backend and he mentioned a possible problem with
savepoints in certain corner cases, but all in all the change should be OK.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 3299-app_id
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1642.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1642
----
commit f88e4d540b71f9a4e683b44a030ad6b267f132cb
Author: Ufuk Celebi <u...@apache.org>
Date: 2016-02-11T15:04:08Z
[FLINK-3299] Remove ApplicationID from Environment
----
> 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)
