CLIENT REPLY
CLIENT REPLY ON | OFF | SKIP
- Group
- Connection
- Complexity
- O(1)
- Arity
- 3 (exactly, counting the command name)
- HotKV Cloud
- All plans
- On-Premise
- no license needed
CLIENT REPLY controls whether the server sends replies to the current
connection. Turning replies off is useful for fire-and-forget bulk loads,
where reading thousands of OK replies would only cost bandwidth.
Options
Section titled “Options”| Mode | Effect |
|---|---|
ON |
Send replies again. This is the default. |
OFF |
Send no replies, from this command on, until CLIENT REPLY ON. |
SKIP |
Send no reply for the next command only. Ignored while replies are OFF. |
Return value
Section titled “Return value”| Case | Reply (RESP2 and RESP3) |
|---|---|
ON |
Simple string OK |
OFF or SKIP |
No reply at all |
| Any other mode | Error ERR syntax error |
Examples
Section titled “Examples”127.0.0.1:6379> CLIENT REPLY SKIP127.0.0.1:6379> SET a 1127.0.0.1:6379> SET b 2OKredis-cli expects a reply to every command, so OFF is best used from a
client library that writes commands without reading replies.
Compatibility
Section titled “Compatibility”Same as Redis 7 and Valkey 8. RESET does not turn replies back on in HotKV.
See also
Section titled “See also”Was this page helpful?
Thanks for the feedback.