Hi Dave,
> The DataStreamer is unordered
Yes, that is absolutely correct.
If I understand correctly, the initial use case is the following:
- there is an initial payload that is streamed into the cluster via
data streamer.
- during that operation, new updates arrive and corresponding
The DataStreamer is unordered. If you have duplicate keys with different
values, and you don't flush or take other action, then you will get an
arbitrary result. AllowOverwrite is not a solution.
Adding to the streamer returns a Future, and all of those futures are
notified when the buffer
Hello,
I don't think there is a way to do that check. Moreover, it seems to me
that is useless in any case.
The thing that allows you to achieve the desired behavior is
`allowOverwrite` flag [1].
By default, the data streamer will not overwrite existing data, which means
that if it will encounter
Hi,
I have a data streamer to load data into a cache. While loading I might need
to update value of a particular key in cache, so I need to check if it is
already there in the streamer buffer. If so, either I need to update value
against that key in the buffer or I need to flush the data in the
