Repository navigation
DOC-7154: Clarify the SCH client-support table - #4216
Merged
Merged
Conversation
…p the failover column Feedback relayed by Mirko Ortensi in Slack on the SCH client-support table: "Basic connection" was ambiguous, and the "Client-side geographic failover" column (all "Disabled") read like a per-client setting. - sch.md: drop the failover column; the existing note already states the limitation and is kept word for word (no change to the published "no"). Move that note ahead of the StackExchange.Redis note since it now applies to every client. - sch.md + redis-py/nodejs/go connect.md SCH version notes: "basic connections" -> "standard routing", defined once on sch.md as any connection that doesn't use the OSS Cluster API. "Standard routing" was Andy's choice from the options Mirko heard; the term didn't exist anywhere in content/ before. The nearest existing term, "Enterprise clustering" (an RS endpoint-configuration setting), was rejected because load-balancer setups are also non-OSS-Cluster-API. Do not rename the "## Basic connection" headings on the connect pages: there "basic" means "simplest connection", a different sense. Lettuce and .NET SCH sections have no basic/cluster version note, so nothing to change there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at 75003c3 |
Contributor
Contributor
Author
|
Thanks @dwdougherty ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses feedback on the SCH client-support table (DOC-7154).
Changes
The
## Basic connectionheadings on the client connect pages are not changed. There, "basic" means the simplest way to connect, which is a different meaning.Review focus
"Standard routing" is a new term in the docs. Please flag it if product uses a different name for non-OSS-Cluster-API connections.
🤖 Generated with Claude Code
Note
Low Risk
Documentation-only terminology and table layout changes with no runtime or API impact.
Overview
Clarifies Smart client handoffs (SCH) client-support documentation by replacing the misleading "Basic connection" label with "Standard routing" and defining it once as any connection that does not use the OSS Cluster API.
On
sch.md, the support table is narrowed to Standard routing and OSS Cluster API only; the Client-side geographic failover column is removed because every row was "Disabled." That limitation is kept in a note under the table (moved above the StackExchange.Redis experimental note so it reads as a global constraint). Matching SCH version callouts on the go-redis, node-redis, and redis-py connect pages now say "standard routing" instead of "basic connections."## Basic connectionsections on connect pages are unchanged—they still mean the simplest connect example, not SCH routing mode.Reviewed by Cursor Bugbot for commit 75003c3. Bugbot is set up for automated code reviews on this repo. Configure here.