Support TTL and reloadData

[tuanpavn]

Please add TTL and loadData function into config so it can auto reload an item if it is expired.

[barkanido]

Ttl eviction is highly valuable!

[manishrjain]

We can do TTL based expiry. But load on TTL seems like a cumbersome design.

[barkanido]

Agreed, just invalidate items due to TTL and let the client decide.

[songboyu]

hello, could I ask when would you plan to add the ttl feature? I think it is necessary

[MarcSky]

Yes we need ttl

[MarcSky]

For example, I want than 1 key living 10second and after reload

[karlmcguire]

Will be working on this over the next few days.

[caofengl]

Will be working on this over the next few days.
May I ask when the master can join the ttl function?

[momilo]

If I may join the discussion... It might be worth considering adding automated purging of expired items.

Ristretto currently seems to be focusing on a scenario where there is a huge amount of data, only a portion of which can be stored in pre-defined size of cache, and it is stored forever (i.e. MaxCost is reached quickly; some additional keys are tracked - NumCounters).

However, many use-cases require a TTL-driven cache, whereby you have to / are happy to cache everything as long as ... e.g. it is max 5 minutes old (e.g. for operations which tend to always be resolved within 1-2 minutes). Hence you would expect the MaxCost to be large (just in case ever needed) but the average cache size would be minimal. A go routine checking expiry times and deleting entries would be needed - and highly appreciated.

I would be happy to help with coding this. Currently it seems like karlmcguire and caofengl are already on it, but feel free to reach out to me if some extra help is needed.