kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Minkovsky (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5105) ReadOnlyKeyValueStore range scans are not ordered
Date Fri, 02 Feb 2018 21:14:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Minkovsky updated KAFKA-5105:
------------------------------------
    Description: 
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.

  was:
_emphasized text_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.


> 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)

Mime
View raw message