Feedback: Data type commands compatibility

[uglide]

Page https://redis.io/docs/latest/operate/rs/references/compatibility/commands/data-types

The following multi-key commands should have a note to warn users about potential cross-slot errors:

For Active-Active or clustered databases, the original key and new key must be in the same hash slot.

• Hyperloglog:
  • PFCOUNT
  • PFMERGE
• Set:
  • SDIFF
  • SDIFFSTORE
  • SMOVE
  • SINTERCARD
  • SINTERSTORE
  • SUNION
  • SUNIONSTORE
• Stream:
  • XREAD
• String:
  • msetnx
  • LCS
• RTS:
  • TSMADD
• Sorted set:
  • bzmpop
  • zdiffstore
  • bzpopmax
  • bzpopmin
  • zunioin
  • zrangestore
• Bitmap:
  • bitop
• List:
  • Lmove
  • blpop
  • brpop
  • lmpop

The list is not complete and needs to be cross-checked.

[dwdougherty]

Thank you, @uglide!

Hi @LiorKogan. If the above list is not complete, can you supply a complete list?

[LiorKogan]

There are 5 configurations we need to analyze

• OSS/RS clustering disabled
• OSS, clustering enabled
• RS, clustering enabled, OSS cluster API enabled
• RS, clustering enabled, OSS cluster API disabled
• RS, active-active (RS is considered clustered even if there is just one shard)

and for each configuration and command, there are 3 possible behaviors:

• single-slot
• cross-slot (all shards)
• cross-slot (within a single shard) - this is a special behavior of some commands.

I believe @uglide 's list is accurate, but I think we should add a table for all 5 configurations.

I prepared a list here: https://redislabs.atlassian.net/browse/RED-132359

Note that this list should contain all multi-key commands (where keys are specified explicitly or are implicit).