Shared Dictionary expiry

mat999 · 2014-04-04T20:48:06+00:00

Hello! On Sat, Apr 5, 2014 at 12:59 PM, vitaly rybalchenko wrote: > I mean when will implement the following features > > implement the SSL cosocke...

Shared Dictionary expiry

mat999

Hi all, Quick Question.

Does using .incr() on a key reset its expiry?

If not, is it possible to (re)set the expiry on a key without setting the value (i.e in a locking safe way).

Thanks in advance,

Mathew

brian

incr does not reset expiry and there currently is no way to update expire without setting a value. Expire times are internally set to absolute times rather than ttl's. I suppose an option table to incr/decr could set a new ttl. Also a "touch" command may be useful. If someone had time, these would be fairly easy to add.

agentzh

Hello!

On Fri, Apr 4, 2014 at 6:44 AM, Brian Akins wrote:
> incr does not reset expiry and there currently is no way to update expire
> without setting a value. Expire times are internally set to absolute times
> rather than ttl's.  I suppose an option table to incr/decr could set a new
> ttl. Also a "touch" command may be useful. If someone had time, these would
> be fairly easy to add.
>

I think a "expire" command (similar to Redis's) is more flexible than
"touch" and it is a good thing to have :)

See

    http://redis.io/commands/expire

And yeah, volunteers welcome!

Best regards,
-agentzh

mat999

I am working on an additional (optional) parameter to incr/decr now to do just this.

On Saturday, April 5, 2014 12:44:58 AM UTC+11, Brian Akins wrote:

incr does not reset expiry and there currently is no way to update expire without setting a value. Expire times are internally set to absolute times rather than ttl's. I suppose an option table to incr/decr could set a new ttl. Also a "touch" command may be useful. If someone had time, these would be fairly easy to add.

mat999

I think both methods have their merits.

.incr / .decr - less lookups / locking

.expire or .touch - more wider application

I am going to implement .incr / .decr in a branch now, I may do .expire in the future if I ever need it.

On Saturday, April 5, 2014 5:22:05 AM UTC+11, agentzh wrote:

Hello!

On Fri, Apr 4, 2014 at 6:44 AM, Brian Akins wrote:
> incr does not reset expiry and there currently is no way to update expire
> without setting a value. Expire times are internally set to absolute times
> rather than ttl's. I suppose an option table to incr/decr could set a new
> ttl. Also a "touch" command may be useful. If someone had time, these would
> be fairly easy to add.
>

I think a "expire" command (similar to Redis's) is more flexible than
"touch" and it is a good thing to have :)

See

http://redis.io/commands/expire

And yeah, volunteers welcome!

Best regards,
-agentzh

mat999

Pull request submitted - https://github.com/chaoslawful/lua-nginx-module/pull/358

Nice and simple I hope. My first time messing with the lua internals so feel free to let me know if mistakes have been made.

I gave the argument the default value of -1 so that if 0 is provided the argument can set the key to not expire.

On Saturday, April 5, 2014 11:55:16 AM UTC+11, Mathew Heard wrote:

I think both methods have their merits.

.incr / .decr - less lookups / locking
.expire or .touch - more wider application

I am going to implement .incr / .decr in a branch now, I may do .expire in the future if I ever need it.

On Saturday, April 5, 2014 5:22:05 AM UTC+11, agentzh wrote:
Hello!

On Fri, Apr 4, 2014 at 6:44 AM, Brian Akins wrote:
> incr does not reset expiry and there currently is no way to update expire
> without setting a value. Expire times are internally set to absolute times
> rather than ttl's. I suppose an option table to incr/decr could set a new
> ttl. Also a "touch" command may be useful. If someone had time, these would
> be fairly easy to add.
>

I think a "expire" command (similar to Redis's) is more flexible than
"touch" and it is a good thing to have :)

See

http://redis.io/commands/expire

And yeah, volunteers welcome!

Best regards,
-agentzh