[
https://issues.apache.org/jira/browse/FLINK-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16089798#comment-16089798
]
ASF GitHub Bot commented on FLINK-7213:
---------------------------------------
GitHub user StefanRRichter opened a pull request:
https://github.com/apache/flink/pull/4353
[FLINK-7213] Introduce state management by OperatorID in TaskManager
Flink-5892 introduced the job manager / checkpoint coordinator part of
managing state on the operator level instead of the task level by introducing
explicit operator_id -> state mappings.
However, this explicit mapping was not introduced in the task manager side,
so the explicit mapping is still converted into a mapping that suits the
implicit operator chain order.
This PR introduces this part and offers explicit state management by
operator_id in the task manager.
Furthermore, this PR also introduces `TaskStateSnapshot` as unify
abstraction to replace `TaskStateHandles` and `SubtaskState`which were always
very similar, except that one offered collections of state handles (to support
scaling in on restore) while the other only contained single objects (because
each state is snapshotted into one state handle).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/StefanRRichter/flink tmpBU
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4353.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 #4353
----
commit d68dd39b343595120f62fc8280b2f3c5f0ee7503
Author: Stefan Richter <[email protected]>
Date: 2017-06-26T16:07:59Z
[FLINK-7213] Introduce state management by OperatorID in TaskManager
commit 11cdd85668aa18f8e5bab0e6cac9ba082bfea95c
Author: Stefan Richter <[email protected]>
Date: 2017-07-11T15:10:03Z
[FLINK-7213] Introduce TaskStateSnapshot to unify TaskStateHandles and
SubtaskState
----
> Introduce state management by OperatorID in TaskManager
> -------------------------------------------------------
>
> Key: FLINK-7213
> URL: https://issues.apache.org/jira/browse/FLINK-7213
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Affects Versions: 1.4.0
> Reporter: Stefan Richter
> Assignee: Stefan Richter
>
> Flink-5892 introduced the job manager / checkpoint coordinator part of
> managing state on the operator level instead of the task level by introducing
> explicit operator_id -> state mappings. However, this explicit mapping was
> not introduced in the task manager side, so the explicit mapping is still
> converted into a mapping that suits the implicit operator chain order.
> We should also introduce explicit operator ids to state management on the
> task manager.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
