-
Notifications
You must be signed in to change notification settings - Fork 100
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 data structure —— Expiring key #142
Comments
I want to receive tasks from ID1 to 11 |
Sure. Can you give me a rough idea of what you think about it? |
Based on the above requirements, we might consider directly storing the expiration time corresponding to the key, and then check whether it's expired when accessing the key. If there are more requirements, please let me know. |
ok, no problem |
Do the keys also need to have values associated with them? |
Perhaps, but this issue has already been claimed, sorry. |
Can you explain the "ex" parameter? Or, could you provide an example to illustrate the usage of "EXPIREBY key duration ex"? |
"ex" is a flag indicating that the "duration" is relative to the current time. If "ex" is not specified, the "duration" is an absolute timestamp. Example: Now, let's set an expiration time of 60 seconds for the key "mykey": This command sets the expiration time of "mykey" to 60 seconds from the current time. After 60 seconds, the key is automatically removed from the database, making it no longer accessible. |
Ok, got it |
Implement all functions of ExpireStructure(#142 ID 1~11)
We need a new data structure, Expiring key, to extend the database's key-value storage structure.
We need to build some instructions into Expiring key to make it more complete.
If you are interested in extending the Expiring key data structure, you can comment below on the issue id you would like to try and we will assign it to you.
The text was updated successfully, but these errors were encountered: