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

[NEW] Add support for expiry of fields in hash key #1047

Closed
tugtugtug opened this issue Sep 18, 2024 · 4 comments
Closed

[NEW] Add support for expiry of fields in hash key #1047

tugtugtug opened this issue Sep 18, 2024 · 4 comments

Comments

@tugtugtug
Copy link

The problem/use-case that the feature addresses

There are many cases one would like to have volatile cache entries but also grouped under a hash table. The popular way to workaround it today is to set a timestamp to the hashed value, and manually calculate the expiry.
This is a long asked feature for redis, and redis started the support of it starting 7.4, and forks of it such as KeyDB has supported years ago.

Description of the feature

Allow similar expiry that one would set to a key to the hash key(fields)

Alternatives you've considered

We currently just carry the timestamp within the value of the key, but obviously this is subject to race and issues like time drift among the clients.

Additional information

N/A

@ranshid
Copy link
Member

ranshid commented Sep 23, 2024

We should merge the requests in a single place, probably: #640
@tugtugtug can you +1 there?

@tugtugtug
Copy link
Author

Thanks @ranshid , agreed, the referenced issue looks identical to my request.

@ranshid
Copy link
Member

ranshid commented Sep 24, 2024

ack then I will close this as duplicate

@ranshid ranshid closed this as completed Sep 24, 2024
@ranshid
Copy link
Member

ranshid commented Sep 24, 2024

duplicate of #640

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

2 participants