> However, >> for keys that have been tombstoned, it does return null for me.
Sound like a bug. Can you reliable reproduce this? Would you mind
opening a JIRA?
Can you check if this happens for both cases: caching enabled and
disabled? Or only for once case?
> "No ordering guarantees are provided."
That is correct. Internally, default stores are hash-based -- thus, we
don't give a sorted list/iterator back. You could replace RocksDB with a
custom store though.
-Matthias
On 3/13/17 3:56 PM, Dmitry Minkovsky wrote:
> I am using interactive streams to query tables:
>
> ReadOnlyKeyValueStore<Messages.ByUserAndDate,
> Messages.UserLetter> store
> = streams.store("view-user-drafts",
> QueryableStoreTypes.keyValueStore());
>
> Documentation says that #range() should not return null values. However,
> for keys that have been tombstoned, it does return null for me.
>
> Also, I noticed only just now that "No ordering guarantees are provided." I
> haven't done enough testing or looked at the code carefully enough yet and
> wonder if someone who knows could confirm: is this true? Is this common to
> all store implementations? I was hoping to use interactive streams like
> HBase to scan ranges. It appears this is not possible.
>
> Thank you,
> Dmitry
>
signature.asc
Description: OpenPGP digital signature
