There is no such mechanism.
Caches are rather static structured. They are not supposed to be created or
removed too often.
Cache creation and destruction are cluster-wide operations, that make all
operations stop until they are finished.
But if you really want to do it, you can schedule a task, t
Him first of all, thank you very much for your quick response!
Just wondering, in that case, is there any scheduling job within Ignite that
removes the cache itself after the records are removed due to expiry policy,
so that when I call ignite.cacheNames() we know that it is removed? Thanks
again!
Hi!
The expiry policy will only remove entries, the cache itself is never
removed, you have to do that yourself.
Mikael
Den 2018-07-30 kl. 15:49, skrev okiesong:
Ignite Cache Expiry policy does not remove the cache from cache lists. I have
set it to 2 hrs, but after 2hours, the records
Ignite Cache Expiry policy does not remove the cache from cache lists. I have
set it to 2 hrs, but after 2hours, the records seems to have been removed,
but not the entire cache, as I could find that cache name when I call
ignite.cacheNames(); I was basically using the same example from
https
