[
https://issues.apache.org/jira/browse/KAFKA-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018866#comment-17018866
]
ASF GitHub Bot commented on KAFKA-9445:
---------------------------------------
brary commented on pull request #7984: [WIP: KAFKA-9445] Allow adding changes
to allow serving from a specific partition
URL: https://github.com/apache/kafka/pull/7984
KIP-562 implementation.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
>
> 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)
