Draft: Patch mget in Redis::Cluster for cross-slot safety and efficiency

Draft: Patch mget in Redis::Cluster for cross-slot safety and efficiency redis crossslot keys in request don't hash to the same slot For Redis use cases where you don't want to lose keys, you should only scale Your client must maintain a map of hash slots to the corresponding redisexceptionsresponseerror_ crossslot keys in request don''t hash to the same slot When multi-key commands are executed in a GeminiDB Redis instance, the error CROSSSLOT Keys in request don't hash to the same slot may be

redisexceptionsresponseerror_ crossslot keys in request don''t hash to the same slot Transactions in Redis only occur within the same hash slot, which ensures the highest throughput ERR CROSSSLOT Keys in request don't

redis slot Cross-slot commands: In Redis Cluster, you can't perform operations that involve multiple keys unless they are all part of the same hash slot This means CROSSSLOT Keys in request don't hash to the same slot This error occurs when keys aren't in the same hash slot even though the keys are stored in the same