[
https://issues.apache.org/jira/browse/FLINK-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148586#comment-15148586
]
ASF GitHub Bot commented on FLINK-3299:
---------------------------------------
Github user gyfora commented on the pull request:
https://github.com/apache/flink/pull/1642#issuecomment-184683583
In general the DbStateBackend should not misbehave under the current
assumptions. What Ufuk means is that the DbStateBackend does not make any
assumption about the job parallelism if using the App id (we could change the
job parallelism). This will not hold now but it does not matter as we don't
support this feature yet.
> 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)
