Merge branch 'main' into DOC-3624

Author: rrelledge

build/components/example.py

@@ -19,6 +19,7 @@
     'java': '//',
     'go': '//',
     'c#': '//',
+    'redisvl': '#'
 }
 
 class Example(object):

config.toml

@@ -45,7 +45,7 @@ tagManagerId = "GTM-TKZ6J9R"
 gitHubRepo = "https://github.com/redis/docs"
 
 # Display and sort order for client examples
-clientsExamples = ["Python", "Node.js", "Java", "Go", "C#"]
+clientsExamples = ["Python", "Node.js", "Java", "Go", "C#", "RedisVL"]
 searchService = "/convai/api/search-service"
 ratingsService = "/docusight/api/rate"
 
@@ -56,6 +56,14 @@ rdi_debezium_server_version = "2.3.0.Final"
 rdi_db_types = "cassandra|mysql|oracle|postgresql|sqlserver"
 rdi_cli_latest = "latest"
 
+[params.clientsConfig]
+"Python"={lang="python", quickstartSlug="python/redis-py"}
+"Node.js"={lang="javascript", quickstartSlug="nodejs"}
+"Java"={lang="java", quickstartSlug="java/jedis"}
+"Go"={lang="go", quickstartSlug="go"}
+"C#"={lang="C#", quickstartSlug="dotnet"}
+"RedisVL"={lang="python", quickstartSlug="python/redis-vl"}
+
 # Markup
 [markup]
   [markup.goldmark]

content/commands/json.mget/index.md

@@ -32,6 +32,10 @@ title: JSON.MGET
 ---
 Return the values at `path` from multiple `key` arguments
 
+{{% warning %}}
+All specified keys must reside on the same [hash slot](https://redis.io/docs/latest/operate/oss_and_stack/reference/cluster-spec/#key-distribution-model).
+{{% /warning %}}
+
 [Examples](#examples)
 
 ## Required arguments

content/commands/json.mset/index.md

@@ -43,6 +43,9 @@ Set or update one or more JSON values according to the specified `key`-`path`-`v
 
 A JSON value is a hierarchical structure. If you change a value in a specific path - nested values are affected.
 
+{{% warning %}}
+All specified keys must reside on the same [hash slot](https://redis.io/docs/latest/operate/oss_and_stack/reference/cluster-spec/#key-distribution-model).
+{{% /warning %}}
 
 [Examples](#examples)
 

content/develop/connect/clients/go.md

@@ -173,8 +173,37 @@ telnet: Unable to connect to remote host: Connection refused
 If you use Docker, Istio, or any other service mesh/sidecar, make sure the app starts after the container is fully available, for example, by configuring healthchecks with Docker and holdApplicationUntilProxyStarts with Istio. 
 For more information, see [Healthcheck](https://docs.docker.com/engine/reference/run/#healthcheck).
 
+### Observability
+
+To monitor go-redis performance and trace the execution of Redis commands, you can install OpenTelemetry instrumentation:
+
+```go
+import (
+    "github.com/redis/go-redis/v9"
+    "github.com/redis/go-redis/extra/redisotel/v9"
+)
+
+rdb := redis.NewClient(&redis.Options{...})
+
+// Enable tracing instrumentation.
+if err := redisotel.InstrumentTracing(rdb); err != nil {
+	panic(err)
+}
+
+// Enable metrics instrumentation.
+if err := redisotel.InstrumentMetrics(rdb); err != nil {
+	panic(err)
+}
+```
+
+The code above instruments Redis commands to collect traces, logs, and metrics. You can find the full example on [GitHub](https://github.com/redis/go-redis/blob/master/example/otel/README.md).
+
+OpenTelemetry is a vendor-agnostic observability framework that allows you to export data to Prometheus, Jaeger, Uptrace, and more. OpenTelemetry supports [distributed tracing](https://uptrace.dev/opentelemetry/distributed-tracing.html), metrics, and logs.
+
+You can also use OpenTelemetry for [monitoring Redis Server](https://uptrace.dev/blog/redis-monitoring.html) performance metrics, which works by periodically executing the Redis `INFO` command and turning results into [OpenTelemetry metrics](https://uptrace.dev/opentelemetry/metrics.html).
+
 ### Learn more
 
 * [Documentation](https://redis.uptrace.dev/guide/)
 * [GitHub](https://github.com/redis/go-redis)
- 
+ 

content/develop/connect/clients/python/_index.md

@@ -0,0 +1,26 @@
+---
+categories:
+- docs
+- develop
+- stack
+- oss
+- rs
+- rc
+- oss
+- kubernetes
+- clients
+hideListLinks: true
+description: Connect your application to a Redis database using Python and try an example
+linkTitle: Python
+title: Connect with Redis Python clients
+weight: 4
+---
+
+You have two choices of Python clients that you can use with Redis:
+
+-   [Redis Python library (redis-py)]({{< relref "/develop/connect/clients/python/redis-py" >}})
+-   [Redis vector library (RedisVL)]({{< relref "/develop/connect/clients/python/redis-vl" >}})
+
+You can also access Redis with an object-mapping client interface. See
+[RedisOM for Python]({{< relref "/integrate/redisom-for-python" >}})
+for more information.

content/develop/connect/clients/python.md renamed to content/develop/connect/clients/python/redis-py.md

@@ -10,8 +10,8 @@ categories:
 - kubernetes
 - clients
 description: Connect your Python application to a Redis database
-linkTitle: Python
-title: Python guide
+linkTitle: Redis Python library
+title: Redis Python library guide
 weight: 1
 ---
 

content/develop/connect/clients/python/redis-vl.md

@@ -0,0 +1,18 @@
+---
+categories:
+- docs
+- develop
+- stack
+- oss
+- rs
+- rc
+- oss
+- kubernetes
+- clients
+description: Connect your Python vector application to a Redis vector database
+linkTitle: Redis vector library
+title: Redis vector library guide
+weight: 1
+---
+
+See the [RedisVL Guide]({{< relref "/integrate/redisvl" >}}) for more information.

content/develop/get-started/vector-database.md

@@ -134,7 +134,7 @@ Iterate over all the Redis keys with the prefix `bikes:`:
 
 {{< clients-example search_vss get_keys />}}
 
-Use the keys as input to the [JSON.MGET]({{< baseurl >}}/commands/json.mget//) command, along with the `$.description` field, to collect the descriptions in a list. Then, pass the list of descriptions to the `.encode()` method:
+Use the keys as input to the [JSON.MGET]({{< baseurl >}}/commands/json.mget/) command, along with the `$.description` field, to collect the descriptions in a list. Then, pass the list of descriptions to the `.encode()` method:
 
 {{< clients-example search_vss generate_embeddings />}}
 

content/develop/reference/modules/modules-api-ref.md

@@ -114,7 +114,7 @@ You should avoid using `calloc()` directly.
 
     void *RedisModule_TryCalloc(size_t nmemb, size_t size);
 
-**Available since:** unreleased
+**Available since:** 7.4.0
 
 Similar to [`RedisModule_Calloc`](#RedisModule_Calloc), but returns NULL in case of allocation failure, instead
 of panicking.
@@ -135,7 +135,7 @@ Use like `realloc()` for memory obtained with [`RedisModule_Alloc()`](#RedisModu
 
     void *RedisModule_TryRealloc(void *ptr, size_t bytes);
 
-**Available since:** unreleased
+**Available since:** 7.4.0
 
 Similar to [`RedisModule_Realloc`](#RedisModule_Realloc), but returns NULL in case of allocation failure,
 instead of panicking.
@@ -467,7 +467,7 @@ Returns `REDISMODULE_OK` on success and `REDISMODULE_ERR` in case of the followi
 
     int RedisModule_AddACLCategory(RedisModuleCtx *ctx, const char *name);
 
-**Available since:** unreleased
+**Available since:** 7.4.0
 
 [`RedisModule_AddACLCategory`](#RedisModule_AddACLCategory) can be used to add new ACL command categories. Category names
 can only contain alphanumeric characters, underscores, or dashes. Categories can only be added
@@ -5268,7 +5268,7 @@ With the following effects:
 
     unsigned int RedisModule_ClusterKeySlot(RedisModuleString *key);
 
-**Available since:** unreleased
+**Available since:** 7.4.0
 
 Returns the cluster slot of a key, similar to the `CLUSTER KEYSLOT` command.
 This function works even if cluster mode is not enabled.
@@ -5279,7 +5279,7 @@ This function works even if cluster mode is not enabled.
 
     const char *RedisModule_ClusterCanonicalKeyNameInSlot(unsigned int slot);
 
-**Available since:** unreleased
+**Available since:** 7.4.0
 
 Returns a short string that can be used as a key or as a hash tag in a key,
 such that the key maps to the given cluster slot. Returns NULL if slot is not