ASF GitHub Bot commented on FLINK-4556:

GitHub user StefanRRichter opened a pull request:


    [FLINK-4556] Make Queryable State Key-Group Aware

    This PR addresses [FLINK-4556]  and makes queryable state aware of 

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

    $ git pull https://github.com/StefanRRichter/flink key-group-queryable-state

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


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2523
commit aeb2033383418fe7015b28a71f6ef6c74039acb2
Author: Stefan Richter <s.rich...@data-artisans.com>
Date:   2016-09-20T14:36:16Z

    [FLINK-4556] Make Queryable State Key-Group Aware


> Make Queryable State Key-Group Aware
> ------------------------------------
>                 Key: FLINK-4556
>                 URL: https://issues.apache.org/jira/browse/FLINK-4556
>             Project: Flink
>          Issue Type: Bug
>          Components: Streaming
>    Affects Versions: 1.2.0
>            Reporter: Aljoscha Krettek
>            Assignee: Stefan Richter
>            Priority: Blocker
> The recent introduction of key-grouped state breaks queryable state because 
> the JobManager does not yet forward the client to the correct TaskManager 
> based on key-group ranges.
> This will either have to be implemented on the JobManager side, i.e. in 
> {{AkkaKvStateLocationLookupService}} or on the {{TaskManager}} when state is 
> registered. The JobManager can know the mapping because it should know the 
> {{parallelism}}/{{maxParallelism}} which it can use to determine where the 
> state for a key-group is stored. The {{TaskManager}} send a 
> {{NotifyKvStateRegistered}} message that already contains a {{keyGroupIndex}} 
> field that is not useful/correct at the moment, though.

This message was sent by Atlassian JIRA

Reply via email to