When using set aggregation operations, if some key does not exists. curiodb return ErrorReply.
but in redis, it ignores the empty.
here is the test:
127.0.0.1:6379> keys *
1) "website2"
2) "website1"
127.0.0.1:6379> smembers website1
1) "google.com"
2) "baidu.com"
127.0.0.1:6379> sunion website1 website3
"ErrorReply"
The reason is in commands.conf, default value of set is seq, when convert to mutable.set is nil.
after change:
127.0.0.1:6379> sunion website1 website3
1) "google.com"
2) "baidu.com"
When using set aggregation operations, if some key does not exists. curiodb return ErrorReply. but in redis, it ignores the empty. here is the test: 127.0.0.1:6379> keys * 1) "website2" 2) "website1" 127.0.0.1:6379> smembers website1 1) "google.com" 2) "baidu.com" 127.0.0.1:6379> sunion website1 website3 "ErrorReply"
The reason is in commands.conf, default value of set is seq, when convert to mutable.set is nil. after change: 127.0.0.1:6379> sunion website1 website3 1) "google.com" 2) "baidu.com"