[
https://issues.apache.org/jira/browse/FLINK-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek updated FLINK-4556:
------------------------------------
Issue Type: Bug (was: Improvement)
> 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
> 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
(v6.3.4#6332)
