-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Support EXPIRETIME and PEXPIRETIME #2083
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm trying to grok the TTL bits and intent but tried to add initial thoughts on everything - this being an overload change is a bit more to consider!
Making diff a bit easier to parse here and simplifying a bit while I'm at it.
@Avital-Fine need a break for staring at this and a few doc tweaks, but think it's close with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@slorello89 I think this is good but I've also been staring at and tweaking it a while, would appreciate an external set of eyes when time allows <3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Continue #2083 Now when we can overload function - we can do it also to `KeyExpire` and `KeyExpireAsync`
Since the method returns TimeSpan and not a number like the redis server (similar to OBJECT IDLETIME), PEXPIRETIME has no difference from EXPIRETIME.
https://redis.io/commands/expiretime/
https://redis.io/commands/pexpiretime/
#2055