Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enterprise "expiringmap". #83

Open
GianniAntini opened this issue Jun 14, 2023 · 2 comments
Open

Enterprise "expiringmap". #83

GianniAntini opened this issue Jun 14, 2023 · 2 comments

Comments

@GianniAntini
Copy link

I Jonathan,

i'm using your map with great satisfaction. I wanted to know if you know of any tools to do the same thing at an enterprise level (especially for use with multiple pods).

I've had a look at redis or hazelcast, but they don't seem to have the option to set different expirations for each key.

thanks

@jhalterman
Copy link
Owner

Hi @GianniAntini Unfortunately there's nothing that I offer or that I'm aware of that does per-key expiration for a replicated map.

@r0bb3n
Copy link

r0bb3n commented Aug 23, 2023

Hi @GianniAntini ,

they don't seem to have the option to set different expirations for each key

at least for redis, this is not true, see the SET command (docs). It supports several ways to do that for each entry:

SET key value [NX | XX] [GET] [EX seconds | PX milliseconds | EXAT unix-time-seconds | PXAT unix-time-milliseconds | KEEPTTL]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants