[jira] [Commented] (FLINK-7213) Introduce state management by OperatorID in TaskManager

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114589#comment-16114589 ] 

ASF GitHub Bot commented on FLINK-7213:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/4353
  
    I had a very rough look at it, and the conceptual rework looks very good.
    
    This would need a detailed pass over the code changes, though, since it touches very sensitive code...


> 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)