Hi Fsapei,
Ignite supports dynamic caches, so you can create and destroy caches on the
fly:
https://apacheignite.readme.io/docs/data-grid#section-jcache
To support your use case, you can:
1. create a new cache and start populating it
2. while the new cache is populated, the queries should go to
It could be 100's or even 1000's of objects..
Say we have Object A is related to Object B we need a way of expressing the
association so that we can navigate from one to the other.
it's a many to many association type idea.. If we co-locate the association
cache with the source, then we cannot
Hi,
You should not serialize cache instances. Actually your cache is already
created on all nodes of your cluster and you can obtain it using
ignite.cache() or ignite.getOrCreateCache() methods.
I assume that you try to start Ignite instance with default name from your
ComplexObjectProcessor but