From 75003c30553c4d6f5a69222b9de9d864d2abc44a Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Tue, 6 Oct 2026 10:51:32 +0100 Subject: [PATCH] DOC-7154: rename SCH "Basic connection" to "Standard routing" and drop 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 --- content/develop/clients/go/connect.md | 2 +- content/develop/clients/nodejs/connect.md | 2 +- content/develop/clients/redis-py/connect.md | 2 +- content/develop/clients/sch.md | 31 +++++++++++---------- 4 files changed, 19 insertions(+), 18 deletions(-) diff --git a/content/develop/clients/go/connect.md b/content/develop/clients/go/connect.md index 716196abe8..49d465cc73 100644 --- a/content/develop/clients/go/connect.md +++ b/content/develop/clients/go/connect.md @@ -138,7 +138,7 @@ for more information about SCH. > [!NOTE] > Using SCH with go-redis requires v9.16.0 or later for -> basic connections, and v9.18.0 or later for +> standard routing, and v9.18.0 or later for > [OSS Cluster API](/content/operate/rs/databases/configure/oss-cluster-api.md) connections. By default, `go-redis` always attempts to connect via SCH but falls back to diff --git a/content/develop/clients/nodejs/connect.md b/content/develop/clients/nodejs/connect.md index a806b90d84..eef6f44f27 100644 --- a/content/develop/clients/nodejs/connect.md +++ b/content/develop/clients/nodejs/connect.md @@ -340,7 +340,7 @@ for more information about SCH. > [!NOTE] > Using SCH with node-redis requires v5.9.0 or later for -> basic connections, and v5.11.0 or later for +> standard routing, and v5.11.0 or later for > [OSS Cluster API](/content/operate/rs/databases/configure/oss-cluster-api.md) connections. Use the configuration options shown in the example below to enable SCH diff --git a/content/develop/clients/redis-py/connect.md b/content/develop/clients/redis-py/connect.md index e12cbcf680..8b2837aeeb 100644 --- a/content/develop/clients/redis-py/connect.md +++ b/content/develop/clients/redis-py/connect.md @@ -264,7 +264,7 @@ for more information about SCH. > [!NOTE] > Using SCH with redis-py requires v7.0.0 or later for -> basic connections, and v7.2.0 or later for +> standard routing, and v7.2.0 or later for > [OSS Cluster API](/content/operate/rs/databases/configure/oss-cluster-api.md) connections. By default, `redis-py` always attempts to connect via SCH but falls back to diff --git a/content/develop/clients/sch.md b/content/develop/clients/sch.md index b34110d6ed..caef507239 100644 --- a/content/develop/clients/sch.md +++ b/content/develop/clients/sch.md @@ -63,29 +63,30 @@ protocol, which is a requirement for SCH. However, you can configure some parameters, such as the timeouts to use during maintenance. -The table below lists the Redis client libraries that support SCH, -and the versions that added support for basic connections and +The following table lists the Redis client libraries that support SCH, +and the versions that added support for standard routing and for [OSS Cluster API](/content/operate/rs/databases/configure/oss-cluster-api.md) connections. +Standard routing covers any connection that doesn't use the OSS Cluster API. -| Client | Basic connection | OSS Cluster API | Client-side geographic failover | -| :-- | :-- | :-- | :-- | -| [redis-py](/content/develop/clients/redis-py/connect.md#connect-using-smart-client-handoffs-sch) | v7.0.0 | v7.2.0 | Disabled | -| [node-redis](/content/develop/clients/nodejs/connect.md#connect-using-smart-client-handoffs-sch) | v5.9.0 | v5.11.0 | Disabled | -| [Lettuce](/content/develop/clients/lettuce/connect.md#connect-using-smart-client-handoffs-sch) | v7.0.0 | - | Disabled | -| [go-redis](/content/develop/clients/go/connect.md#connect-using-smart-client-handoffs-sch) | v9.16.0 | v9.18.0 | Disabled | -| [StackExchange.Redis](/content/develop/clients/dotnet/connect.md#connect-using-smart-client-handoffs-sch) | v3.3.0 | v3.3.0 | Disabled | +| Client | Standard routing | OSS Cluster API | +| :-- | :-- | :-- | +| [redis-py](/content/develop/clients/redis-py/connect.md#connect-using-smart-client-handoffs-sch) | v7.0.0 | v7.2.0 | +| [node-redis](/content/develop/clients/nodejs/connect.md#connect-using-smart-client-handoffs-sch) | v5.9.0 | v5.11.0 | +| [Lettuce](/content/develop/clients/lettuce/connect.md#connect-using-smart-client-handoffs-sch) | v7.0.0 | - | +| [go-redis](/content/develop/clients/go/connect.md#connect-using-smart-client-handoffs-sch) | v9.16.0 | v9.18.0 | +| [StackExchange.Redis](/content/develop/clients/dotnet/connect.md#connect-using-smart-client-handoffs-sch) | v3.3.0 | v3.3.0 | + +> [!NOTE] +> SCH is currently disabled when a client is configured for +> [Client-side geographic failover](/content/develop/clients/failover.md). +> Integration of the two features is planned for a future release. +  > [!NOTE] > SCH support in StackExchange.Redis is marked `[Experimental]`, so the API may > still change. See > [Connect using Smart client handoffs (SCH)](/content/develop/clients/dotnet/connect.md#connect-using-smart-client-handoffs-sch) > for details. -  - -> [!NOTE] -> SCH is currently disabled when a client is configured for -> [Client-side geographic failover](/content/develop/clients/failover.md). -> Integration of the two features is planned for a future release. ## SCH support in Redis server products