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!
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
