BinaryJedisCommands does not define #select, #mget, #mset, or #msetnx about jedis HOT 4 CLOSED

yes, it seems I just missed those in BinaryJedis. Although there is no Binary Protocol in Redis. BinaryJedis is just a class to be able to send byte stream directly instead of strings.
Will fix this ASAP.

from jedis.

Interesting. I thought there was a textual protocol for Redis with a few reserved characters ('\r', '\n', '\0' and ' ') and then there was a binary protocol that used length+byte[] encoding to get around reserved bytes. Just to confirm -- in BinaryJedis, there are no reserved bytes?

from jedis.

no reserved bytes. everything is safe :)
that's the cool new protocol (which is actually the only one supported actually)

from jedis.

it took sometime, but these commands can't go in BinaryJedisCommands. I should change the name of that interface.
Only shard safe commands are allowed there. This mean commands that can be sharded as they operate on a key. The commands you mention don't operate on a key (like select) or operate on many keys.

The way to use them in a sharded environment is to get the shard you need, with getShard("somekey") and than execute these commands on a regular Jedis class.

Thanks anyway for reporting this!

from jedis.