Skip to content

RS: Fix misleading note about sharded pub/sub & RESP3 #1137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 6, 2025
Merged

RS: Fix misleading note about sharded pub/sub & RESP3 #1137

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/operate/rs/references/compatibility/resp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ To use RESP3 with a Redis Enterprise Software database:
When RESP3 is deactivated, connected clients that use RESP3 are disconnected from the database.

{{<note>}}
You cannot use sharded pub/sub if you deactivate RESP3 support.
You cannot use sharded pub/sub if you deactivate RESP3 support. When RESP3 is enabled, you can use sharded pub/sub with either RESP2 or RESP3.
{{</note>}}

## Change default RESP3 option
Expand Down