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

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

GitHub user shixiaogang opened a pull request:

    https://github.com/apache/flink/pull/3531

    [FLINK-6034][checkpoint] Add KeyedStateHandle for the snapshots in keyed 
streams

    ## Changes
    - Add `KeyedStateHandle` for the snapshots in keyed streams. 
`KeyGroupsStateHandle` now is one of its implementation.
    - Distribute `KeyedStateHandle`s to subtasks with their key group range. A 
`KeyedStateHandle` will be assigned to all  subtasks whose key group range 
overlap with its range.
     

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shixiaogang/flink flink-6034

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3531.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 #3531
    
----
commit 9637dcc40d66a2702f5227b7bbe3ae66fca89adf
Author: xiaogang.sxg <xiaogang....@alibaba-inc.com>
Date:   2017-03-14T11:04:37Z

    Add KeyedStateHandle for the snapshots in keyed streams

----


> Add KeyedStateHandle for the snapshots in keyed streams
> -------------------------------------------------------
>
>                 Key: FLINK-6034
>                 URL: https://issues.apache.org/jira/browse/FLINK-6034
>             Project: Flink
>          Issue Type: Sub-task
>          Components: State Backends, Checkpointing
>            Reporter: Xiaogang Shi
>            Assignee: Xiaogang Shi
>
> Currently, the only type of the snapshots in keyed streams is 
> {{KeyGroupsStateHandle}} which is full and store the states one group after 
> another. With the introduction of incremental checkpointing, we need a higher 
> level abstraction of keyed snapshots to allow flexible snapshot formats. 
> The implementation of {{KeyedStateHandle}} s may vary a lot in different 
> backends. The only information needed in {{KeyedStateHandle}} s is their key 
> group range. When recovering the job with a different degree of parallelism, 
> {{KeyedStateHandle}} s will be assigned to those subtasks whose key group 
> ranges overlap with their ranges.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to