I think persistence through snapshots (Raul proposed the other day) is an
option too.
Since all data structures in Ignite are basically key-value, it should be quite
universal. Ordering can be preserved too.
#This will also require taking care of data updated between snapshots to avoid
data l
I think we need a specialized CollectionStore API for this. Something that
will receive an element value and its index (if index is required).
D.
On Thu, Jan 14, 2016 at 11:31 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Igniters,
>
> It sounds like users could be interested
Igniters,
It sounds like users could be interested in being able to persist the data
saved in queues and sets. See the thread on user list [1].
The obvious solution is to reuse our CacheStore interface, but I'm not sure
that this is possible because it's designed for key-value storage. E.g.,
what