You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that the expires flag just works by respecting that on reads - but since Mongo doesnt implement any native expiring functionality it means that those key/values will just accumulate forever.
Should this be mentioned in the docs? That is, users might want to implement their own expiry sweeping mechanism? Probably just add an index on +expires+ and then sweep it via cron.
The text was updated successfully, but these errors were encountered:
That is true. If flushing expired is necessary some process like this would be needed. I'll leave this open til I doc it a bit in the readme or something.
I see that the expires flag just works by respecting that on reads - but since Mongo doesnt implement any native expiring functionality it means that those key/values will just accumulate forever.
Should this be mentioned in the docs? That is, users might want to implement their own expiry sweeping mechanism? Probably just add an index on +expires+ and then sweep it via cron.
The text was updated successfully, but these errors were encountered: