From f529a01c1b52367b4337119ae8f86fd1d790a5ea Mon Sep 17 00:00:00 2001 From: antirez Date: Mon, 14 Sep 2015 12:28:22 +0200 Subject: [PATCH] MOVE now can move TTL metadata as well. MOVE was not able to move the TTL: when a key was moved into a different database number, it became persistent like if PERSIST was used. In some incredible way (I guess almost nobody uses Redis MOVE) this bug remained unnoticed inside Redis internals for many years. Finally Andy Grunwald discovered it and opened an issue. This commit fixes the bug and adds a regression test. Close #2765. --- src/db.c | 4 +++- tests/unit/keyspace.tcl | 13 +++++++++++++ 2 files changed, 16 insertions(+), 1 deletion(-) diff --git a/src/db.c b/src/db.c index 1100c7ef..df2e50ca 100644 --- a/src/db.c +++ b/src/db.c @@ -743,7 +743,7 @@ void moveCommand(client *c) { robj *o; redisDb *src, *dst; int srcid; - long long dbid; + long long dbid, expire; if (server.cluster_enabled) { addReplyError(c,"MOVE is not allowed in cluster mode"); @@ -777,6 +777,7 @@ void moveCommand(client *c) { addReply(c,shared.czero); return; } + expire = getExpire(c->db,c->argv[1]); /* Return zero if the key already exists in the target DB */ if (lookupKeyWrite(dst,c->argv[1]) != NULL) { @@ -784,6 +785,7 @@ void moveCommand(client *c) { return; } dbAdd(dst,c->argv[1],o); + if (expire) setExpire(dst,c->argv[1],expire); incrRefCount(o); /* OK! key moved, free the entry in the source DB */ diff --git a/tests/unit/keyspace.tcl b/tests/unit/keyspace.tcl index e808aaf9..b66dbb2a 100644 --- a/tests/unit/keyspace.tcl +++ b/tests/unit/keyspace.tcl @@ -193,6 +193,19 @@ start_server {tags {"keyspace"}} { set e } {*ERR*index out of range} + test {MOVE can move key expire metadata as well} { + r select 10 + r flushdb + r select 9 + r set mykey foo ex 100 + r move mykey 10 + assert {[r ttl mykey] == -2} + r select 10 + assert {[r ttl mykey] > 0 && [r ttl mykey] <= 100} + assert {[r get mykey] eq "foo"} + r select 9 + } + test {SET/GET keys in different DBs} { r set a hello r set b world