You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Motivation
I found this issue while trying to support scirpt flag allow-cross-slot-keys
Related discussions in redis: redis/redis#10503 redis/redis#13140
kvrocks currently does not prohibit cross-slot in MULTI-EXEC. Is there any mechanism to provide protection? If not we should ban it.
Solution
I noticed that there is CanExecByMySelf to make relevant judgments, but it seems to be only suitable for checking whether the slots of multiple keys operated by a single command are the same, but does not detect the situation of multiple commands (such as MULTI-EXEC and scirpt). We may need to track multiple Commands using slots.
Are you willing to submit a PR?
I'm willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Search before asking
Motivation
I found this issue while trying to support scirpt flag
allow-cross-slot-keys
Related discussions in redis:
redis/redis#10503
redis/redis#13140
kvrocks currently does not prohibit
cross-slot
inMULTI-EXEC
. Is there any mechanism to provide protection? If not we should ban it.Solution
I noticed that there is
CanExecByMySelf
to make relevant judgments, but it seems to be only suitable for checking whether the slots of multiple keys operated by a single command are the same, but does not detect the situation of multiple commands (such as MULTI-EXEC and scirpt). We may need to track multiple Commands using slots.Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: