The problem/use-case that the feature addresses
Sometimes we need timed based keys for process after too short time.
Description of the feature
We might use SET command with ttc (or something else) argument to create key-value after x sec/ms later.
redis> SET mykey "Hello" TTC 10 EX 30
X = 10
Y = 30
Additional information
There is workaround something like this But It causes many operations from client side.
Comment From: madolson
Hey, I'm not exactly clear what problem you're trying to solve with this. In your example, why don't you want the key to be available for 10 seconds?
Comment From: bduman
I want use redis for task scheduling in multi-instance app.
In this article, it describes another workaround but if this feature added, it might make easier.
Comment From: itamarhaber
Hello @bduman
Have you considered using an existing project? There are already a lot of existing task schedulers out there, many even relying on Redis to function, so why invent a new one? I recommend looking around (e.g. at the bottom of https://redis.io/clients) and picking one that suits your needs. Alternatively, if you want to implement your own, I think the best way to review one of the existing libraries for inspiration and education.
That said, I'm not sure how this feature will help with task scheduling and I can think of a few potential issues with delayed key creation as a concept. Perhaps @bduman could explain the use case in more depth - the first link is an approach for tracking keys' creation time, whereas the second is a basic implementation of a job queue (see existing tools).
Comment From: madolson
The article you mentioned also suggested using sorted sets, which I think makes a lot more sense then the system you mentioned. I'm not really inclined to support this.