You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Dmitry Minkovsky (JIRA)" <ji...@apache.org> on 2018/02/02 21:15:00 UTC
[jira] [Commented] (KAFKA-5105) ReadOnlyKeyValueStore range scans
are not ordered
[ https://issues.apache.org/jira/browse/KAFKA-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350952#comment-16350952 ]
Dmitry Minkovsky commented on KAFKA-5105:
-----------------------------------------
Wondering if anyone knows whether 1.0.0 and up are still affected by this. I still don't entirely understand Damien's explanation for this phenomenon (that it's related to partitions).
> ReadOnlyKeyValueStore range scans are not ordered
> -------------------------------------------------
>
> Key: KAFKA-5105
> URL: https://issues.apache.org/jira/browse/KAFKA-5105
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.2.0
> Reporter: Dmitry Minkovsky
> Priority: Major
>
> Following up with this thread https://www.mail-archive.com/users@kafka.apache.org/msg25373.html
> Although ReadOnlyKeyValueStore's #range() is documented not to returns values in order, it would be great if it would for keys within a single partition. This would facilitate using interactive queries and local state as one would use HBase to index data by prefixed keys. If range returned keys in lexicographical order, I could use interactive queries for all my data needs except search.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)