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
Just a comment/interesting point I noticed while playing around with TTL's in Redis + Ohm + ohm-expire. If you using Redis' in-built expiry then Ohm's id index (key[:all]) won't be in sync. i.e. We're using Ohm to mark records for expiry, but Ohm knows nothing about when Redis expires them, and thus we cannot maintain the key index at the application level.
Not sure this is an issue worth tackling. I suppose if it's important to someone, they can always rebuild the index. Or one just has to be aware that if they are iterating over the collection of id's in that index, its likely that some of those records have already been expired.
Maybe worth noting the same in the README ?
The text was updated successfully, but these errors were encountered:
Hi there
First of all good job on creating this plugin.
Just a comment/interesting point I noticed while playing around with TTL's in Redis + Ohm + ohm-expire. If you using Redis' in-built expiry then Ohm's id index (key[:all]) won't be in sync. i.e. We're using Ohm to mark records for expiry, but Ohm knows nothing about when Redis expires them, and thus we cannot maintain the key index at the application level.
Not sure this is an issue worth tackling. I suppose if it's important to someone, they can always rebuild the index. Or one just has to be aware that if they are iterating over the collection of id's in that index, its likely that some of those records have already been expired.
Maybe worth noting the same in the README ?
The text was updated successfully, but these errors were encountered: