defunkt/redis-namespace — Issue #34: Design Decision: Missing Commands
Author: yaauie
Created: 2012-01-10 00:40:53+00:00
State: open

Should missing commands just be forwarded to redis?

Consider the following scenario:

1. new command supported by `redis-rb` (yay!)
2. people use it under `redis-namespace`, expecting it to be namespaced
3. only to find out later that it is not; an upgrade of `redis-namespace` means taking down the application and manually migrating data.

Wouldn't it be better to find out that a command is not supported while in dev? A warning, at least, if not an outright error?

I ended up with > 500,000 records not-namespaced because I used setbit and getrange, neither of which were namespaced so it worked at a unit test level. When I deployed a change that would expire or delete keys, those functions *were* namespaced, so they didn't work, leading me to find the root cause. Knowing that these functions were not supported while in dev would have saved me a production-scale headache.