sk0x50 commented on issue #10911: URL: https://github.com/apache/ignite/issues/10911#issuecomment-1758075977
Hello @fbutter , > Is the topic of changing the cache configuration at runtime still on your agenda? I don't think so, unfortunately. I could not find any discussions on the dev list that relate to this topic, at least. > Is there a way to set or modify the TTL, used by the "[single thread to clean up expired entries in the background](https://ignite.apache.org/docs/latest/configuring-caches/expiry-policies#eager-ttl)"? It can be done programmatically using `IgniteCache.withExpiryPolicy` method https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#withExpiryPolicy-javax.cache.expiry.ExpiryPolicy- This method returns cache with the specified expired policy set. This policy will be used for each operation invoked on the returned cache. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
