You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2020/01/30 07:47:00 UTC
[jira] [Resolved] (KAFKA-9445) Allow fetching a key from a single
partition rather than iterating over all the stores on an instance
[ https://issues.apache.org/jira/browse/KAFKA-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias J. Sax resolved KAFKA-9445.
------------------------------------
Fix Version/s: 2.5.0
Resolution: Fixed
> Allow fetching a key from a single partition rather than iterating over all the stores on an instance
> -----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-9445
> URL: https://issues.apache.org/jira/browse/KAFKA-9445
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Reporter: Navinder Brar
> Assignee: Navinder Brar
> Priority: Major
> Labels: KIP-562
> Fix For: 2.5.0
>
>
> Whenever a call is made to get a particular key from a Kafka Streams instance, currently it returns a Queryable store that contains a list of the stores for all the running and restoring/replica(with KIP-535) on the instance via StreamThreadStateStoreProvider#stores(). This list of stores is then provided to CompositeReadOnlyKeyValueStore#get() which looks into each store one by one. With the changes that went in as a part of KIP-535 since we have access to the information that a key belongs to which partition, we should have a capability to fetch store for that particular partition and look for key in store for that partition only. It would be a good improvement for improving latencies for applications that contain multiple partitions on a single instance and don't have bloom filters enabled internally for Rocksdb.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)