For a ContinuousQuery, the documentation indicates that the local listener
is guaranteed exactly once delivery of each event.
This is very appealing to me, as I’d like to construct a continuous
debezium-style changelog of the cache.
But I’m having difficulty pinning down a guarantee that every
CacheListenerEvent will represent future activity with respect to the
events pulled off the initial ScanQuery cursor.
Example scenario:
The state of the cache is:
aaa->8
aab->13
…
zzz->40
While (perhaps slowly) iterating over the initial ScanQuery cursor, I get a
CacheListenerEvent zzz->{oldValue: 40, value:60}
Am I still guaranteed to pull zzz->40 off the iterator?
-Adam
