Too many Options in Set operations about scala-redis HOT 5 CLOSED

The outermost Option is for the situation when we get an error reply from Redis server. Please have a look at http://redis.io/topics/protocol.

from scala-redis.

Yep! I should have read Protocol specification before. Sorry!
Now everything clear to me.

from scala-redis.

I've tried to execute "smembers" on key that is not a Set and get Exception: ERR Operation against a key holding the wrong kind of value.
Now I am really confused, because You told that:

The outermost Option is for the situation when we get an error reply from Redis server.

But in fact You fire the exception.
Can You explain this to me, please?

from scala-redis.

In Redis protocol, some of the APIs return a Multi Bulk Protocol, which is documented in http://redis.io/topics/protocol. If you go towards the end of this document, you will see a discussion on Null Multi Bulk Reply. It says ..

Also the concept of Null Multi Bulk Reply exists.
For instance when the BLPOP command times out, it returns a Null Multi Bulk Reply, that has a count of -1 as in the following example:
C: BLPOP key 1
S: *-1\r\n

Note here redis returns -1 after the MULTI (*). In such cases the client returns a None. The Redis protocol documentation contains this example with BLPOP. But there can be scenarios with other multi-bulk replies where -1 is returned after a MULTI. Hence for safety I have made this distinction.

from scala-redis.

Thank You!

from scala-redis.