Merge branch 'main' into release-rs-gilboa

Author: rrelledge

build/components/example.py

@@ -26,7 +26,10 @@
     'go': '//',
     'c#': '//',
     'redisvl': '#',
-    'php': '//'
+    'php': '//',
+    'rust': '//',
+    'rust-sync': '//',
+    'rust-async': '//'
 }
 
 

build/local_examples.py

@@ -25,7 +25,8 @@
     '.go': 'go',
     '.cs': 'c#',
     '.java': 'java',
-    '.php': 'php'
+    '.php': 'php',
+    '.rs': 'rust'
 }
 
 # Language to client name mapping (from config.toml clientsExamples)
@@ -36,7 +37,8 @@
     'c#': 'C#',
     'java': 'Java-Sync',  # Default to sync, could be overridden
     'php': 'PHP',
-    'redisvl': 'RedisVL'
+    'redisvl': 'RedisVL',
+    'rust': 'Rust-Sync'
 }
 
 
@@ -65,6 +67,11 @@ def get_client_name_from_language_and_path(language: str, path: str) -> str:
             return 'Java-Async'
         if 'lettuce-reactive' in path:
             return 'Java-Reactive'
+    if language == 'rust':
+        if 'rust-async' in path:
+            return 'Rust-Async'
+        if 'rust-sync' in path:
+            return 'Rust-Sync'
     # Default behavior for all languages (and Java fallback)
     return get_client_name_from_language(language)
 

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-Sync", "Java-Async", "Java-Reactive", "Go", "C#", "RedisVL", "PHP"]
+clientsExamples = ["Python", "Node.js", "Java-Sync", "Java-Async", "Java-Reactive", "Go", "C#", "RedisVL", "PHP", "Rust-Sync", "Rust-Async"]
 searchService = "/convai/api/search-service"
 ratingsService = "/docusight/api/rate"
 
@@ -67,6 +67,8 @@ rdi_current_version = "1.14.1"
 "C#"={quickstartSlug="dotnet"}
 "RedisVL"={quickstartSlug="redis-vl"}
 "PHP"={quickstartSlug="php"}
+"Rust-sync"={quickstartSlug="rust"}
+"Rust-async"={quickstartSlug="rust"}
 
 # Markup
 [markup]

content/develop/clients/_index.md

@@ -19,7 +19,7 @@ weight: 30
 
 Use the Redis client libraries to connect to Redis servers from
 your own code. We document the following client libraries
-for seven main languages:
+for eight main languages:
 
 | Language | Client name | Docs | Supported |
 | :-- | :-- | :-- | :-- |
@@ -32,6 +32,7 @@ for seven main languages:
 | [Go](https://go.dev/) | [`go-redis`](https://github.com/redis/go-redis) | [`go-redis` guide]({{< relref "/develop/clients/go" >}}) | Yes |
 | [PHP](https://www.php.net/)| [`Predis`](https://github.com/predis/predis) | [`Predis` guide]({{< relref "/develop/clients/php" >}}) | No |
 | [C](https://en.wikipedia.org/wiki/C_(programming_language)) | [`hiredis`](https://github.com/redis/hiredis) | [`hiredis` guide]({{< relref "/develop/clients/hiredis" >}}) | Yes |
+| [Rust](https://www.rust-lang.org/) | [`redis-rs`](https://github.com/redis-rs/redis-rs) | [`redis-rs` guide]({{< relref "/develop/clients/rust" >}}) | No |
 
 We also provide several higher-level
 [object mapping (OM)]({{< relref "/develop/clients/om-clients" >}})
@@ -51,7 +52,6 @@ Redis does not document directly:
 | [Dart](https://dart.dev/) | redis_dart_link | https://github.com/toolsetlink/redis_dart_link | https://github.com/toolsetlink/redis_dart_link |
 | [PHP](https://www.php.net/) | PhpRedis extension | https://github.com/phpredis/phpredis | https://github.com/phpredis/phpredis/blob/develop/README.md |
 | [Ruby](https://www.ruby-lang.org/en/) | redis-rb | https://github.com/redis/redis-rb | https://rubydoc.info/gems/redis |
-| [Rust](https://www.rust-lang.org/) | redis-rs | https://github.com/redis-rs/redis-rs | https://docs.rs/redis/latest/redis/ |
 
 
 ## Requirements

content/develop/clients/hiredis/_index.md

@@ -12,7 +12,7 @@ categories:
 description: Connect your C application to a Redis database.
 linkTitle: hiredis (C)
 title: hiredis guide (C)
-weight: 9
+weight: 10
 ---
 
 [`hiredis`](https://github.com/redis/hiredis) is the

content/develop/clients/rust/_index.md

@@ -0,0 +1,79 @@
+---
+categories:
+- docs
+- develop
+- stack
+- oss
+- rs
+- rc
+- oss
+- kubernetes
+- clients
+description: Connect your Rust application to a Redis database
+linkTitle: redis-rs (Rust)
+title: redis-rs guide (Rust)
+weight: 9
+---
+
+[`redis-rs`](https://github.com/redis-rs/redis-rs) is the [Rust](https://www.rust-lang.org/) client for Redis.
+The sections below explain how to install `redis-rs` and connect your application to a Redis database.
+
+{{< note >}}Although we provide basic documentation for `redis-rs`, it is a third-party
+client library and is not developed or supported directly by Redis.
+{{< /note >}}
+
+`redis-rs` requires a running Redis server. See [here]({{< relref "/operate/oss_and_stack/install/" >}}) for Redis Open Source installation instructions.
+
+## Install
+
+To use the synchronous API, add the `redis` crate as a dependency in your
+`Cargo.toml` file:
+
+```toml
+[dependencies]
+redis = "0.32.5"
+```
+
+If you want to use the asynchronous API, you should also enable either
+[`tokio`](https://tokio.rs/) or [`smol`](https://crates.io/crates/smol)
+as your async platform:
+
+```toml
+[dependencies]
+# if you use tokio
+tokio = { version = "1.32.0", features = ["full"] }
+redis = { version = "0.32.5", features = ["tokio-comp"] }
+
+# if you use smol
+smol = "2.0.2"
+redis = { version = "0.32.5", features = ["smol-comp"] }
+```
+
+## Connect
+
+Start by importing the `Commands` or `AsyncCommands` trait from the `redis` crate:
+
+{{< clients-example set="landing" step="import" lang_filter="Rust-Sync,Rust-Async" >}}
+{{< /clients-example >}}
+
+The following example shows the simplest way to connect to a Redis server:
+
+{{< clients-example set="landing" step="connect" lang_filter="Rust-Sync,Rust-Async" >}}
+{{< /clients-example >}}
+
+After connecting, you can test the connection by  storing and retrieving
+a simple [string]({{< relref "/develop/data-types/strings" >}}):
+
+{{< clients-example set="landing" step="set_get_string" lang_filter="Rust-Sync,Rust-Async" >}}
+{{< /clients-example >}}
+
+You can also easily store and retrieve a [hash]({{< relref "/develop/data-types/hashes" >}}):
+
+{{< clients-example set="landing" step="set_get_hash" lang_filter="Rust-Sync,Rust-Async" >}}
+{{< /clients-example >}}
+
+## More information
+
+See the [`redis-rs`](https://docs.rs/redis/latest/redis/) documentation
+and the [GitHub repository](https://github.com/redis-rs/redis-rs) for more
+information and examples.

content/integrate/amazon-bedrock/set-up-redis.md

@@ -79,11 +79,11 @@ To set up a Redis Cloud instance for Bedrock, you need to:
 
 1. Select **Amazon Web Services** as the cloud vendor and select a region.
 
-1. In the **Optimal database settings** section:
+1. In the **Database Sizing** section:
 
     {{<image filename="images/rc/pro-easy-create-size-throughput.png" alt="The Dataset size, throughput, and High availability settings.">}}
 
-    - Turn on [**High-availability**]({{< relref "/operate/rc/databases/configuration/high-availability" >}}).
+    - Select [**High availability**]({{< relref "/operate/rc/databases/configuration/high-availability" >}}) if it is not already selected.
     - Set the Dataset size of your database based on the amount of data that Bedrock will pull from your Simple Storage Service (S3) [bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html). See [Find out the size of your S3 buckets](https://aws.amazon.com/blogs/storage/find-out-the-size-of-your-amazon-s3-buckets/) to find out how much knowledge base data is stored in your S3 bucket and pick the closest size, rounded up, from the table below. 
 
         | Total Size of Documents in S3 | Database size without replication | Database size with replication |

content/integrate/prometheus-with-redis-cloud/_index.md

@@ -25,6 +25,12 @@ Redis Cloud exposes its metrics through a Prometheus endpoint. You can configure
 
 The Redis Cloud Prometheus endpoint is exposed on Redis Cloud's internal network. To access this network, enable [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}}) or [Private Service Connect]({{< relref "/operate/rc/security/private-service-connect" >}}). Both options are only available with Redis Cloud Pro. You cannot use Prometheus and Grafana with Redis Cloud Essentials.
 
+  {{< note >}}
+  
+The Prometheus endpoint's metrics cover all databases within a subscription. Any database added to or removed from the subscription is reflected automatically. 
+
+  {{< /note >}}
+
 For more information on how Prometheus communicates with Redis Enterprise clusters, see [Prometheus integration with Redis Enterprise Software]({{< relref "/integrate/prometheus-with-redis-enterprise/" >}}).
 
 ## Quick start

content/integrate/redis-data-integration/installation/install-k8s.md

@@ -323,10 +323,12 @@ section to learn how to do this.
 
 When the Helm installation is complete and you have prepared the source database for CDC,
 you are ready to start using RDI.
-Use [Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}}) to
+Use [Redis Insight]({{< relref "/develop/tools/insight" >}}) to
 [configure]({{< relref "/integrate/redis-data-integration/data-pipelines" >}}) and
 [deploy]({{< relref "/integrate/redis-data-integration/data-pipelines/deploy" >}})
-your pipeline.
+your pipeline (see
+[RDI in Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}})
+for full details on how to do this).
 
 ## Uninstall RDI
 

content/integrate/redis-data-integration/installation/install-vm.md

@@ -266,7 +266,9 @@ you are ready to start using RDI. See the guides on how to
 [configure]({{< relref "/integrate/redis-data-integration/data-pipelines" >}}) and
 [deploy]({{< relref "/integrate/redis-data-integration/data-pipelines/deploy" >}})
 RDI pipelines for more information. You can also configure and deploy a pipeline
-using [Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}}).
+using [Redis Insight]({{< relref "/develop/tools/insight" >}}). See
+[RDI in Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}})
+for full details on how to connect to RDI and deploy pipelines.
 
 ## Uninstall RDI