Revert "Merge branch 'main' into latest"

This reverts commit 7b1b6aa, reversing
changes made to face635.

Author: cmilesb

.github/workflows/redis_docs_sync.yaml

@@ -43,5 +43,5 @@ Here's the list of tracking information sections and their respective values:
   * `caching-no`: The next command won't cache keys (exists only together with `optout`).
   * `noloop`: The client isn't notified about keys modified by itself.
   * `broken_redirect`: The client ID used for redirection isn't valid anymore.
-* **redirect**: The client ID used for notifications redirection, 0 for self-redirection, or -1 when none.
+* **redirect**: The client ID used for notifications redirection, or -1 when none.
 * **prefixes**: A list of key prefixes for which notifications are sent to the client.

content/commands/client-trackinginfo/index.md

@@ -173,7 +173,7 @@ syntax: "FT.AGGREGATE index query \n  [VERBATIM] \n  [LOAD count field [field ..
   \ ...]] ...]] \n  [ SORTBY nargs [ property ASC | DESC [ property ASC | DESC ...]]\
   \ [MAX num] [WITHCOUNT] \n  [ APPLY expression AS name [ APPLY expression AS name\
   \ ...]] \n  [ LIMIT offset num] \n  [FILTER filter] \n  [ WITHCURSOR [COUNT read_size]\
-  \ [MAXIDLE idle_time]] \n  [ PARAMS nargs name value [ name value ...]] \n  [ADDSCORES] \n  [DIALECT\
+  \ [MAXIDLE idle_time]] \n  [ PARAMS nargs name value [ name value ...]] \n  [DIALECT\
   \ dialect]\n"
 syntax_fmt: "FT.AGGREGATE index query [VERBATIM] [LOAD\_count field [field ...]]\n\
   \  [TIMEOUT\_timeout] [LOAD *] [GROUPBY\_nargs property [property ...]\n  [REDUCE\_\
@@ -183,15 +183,15 @@ syntax_fmt: "FT.AGGREGATE index query [VERBATIM] [LOAD\_count field [field ...]]
   name] ...]] ...]]\n  [SORTBY\_nargs [property <ASC | DESC> [property <ASC | DESC>\
   \ ...]]\n  [MAX\_num]] [APPLY\_expression AS\_name [APPLY\_expression AS\_name\n\
   \  ...]] [LIMIT offset num] [FILTER\_filter] [WITHCURSOR\n  [COUNT\_read_size] [MAXIDLE\_\
-  idle_time]] [PARAMS nargs name value\n  [name value ...]]\n  [ADDSCORES]\n  [DIALECT\_dialect]"
+  idle_time]] [PARAMS nargs name value\n  [name value ...]] [DIALECT\_dialect]"
 syntax_str: "query [VERBATIM] [LOAD\_count field [field ...]] [TIMEOUT\_timeout] [LOAD\
   \ *] [GROUPBY\_nargs property [property ...] [REDUCE\_function nargs arg [arg ...]\
   \ [AS\_name] [REDUCE\_function nargs arg [arg ...] [AS\_name] ...]] [GROUPBY\_nargs\
   \ property [property ...] [REDUCE\_function nargs arg [arg ...] [AS\_name] [REDUCE\_\
   function nargs arg [arg ...] [AS\_name] ...]] ...]] [SORTBY\_nargs [property <ASC\
   \ | DESC> [property <ASC | DESC> ...]] [MAX\_num]] [APPLY\_expression AS\_name [APPLY\_\
   expression AS\_name ...]] [LIMIT offset num] [FILTER\_filter] [WITHCURSOR [COUNT\_\
-  read_size] [MAXIDLE\_idle_time]] [PARAMS nargs name value [name value ...]] [ADDSCORES] [DIALECT\_\
+  read_size] [MAXIDLE\_idle_time]] [PARAMS nargs name value [name value ...]] [DIALECT\_\
   dialect]"
 title: FT.AGGREGATE
 ---
@@ -316,15 +316,6 @@ defines one or more value parameters. Each parameter has a name and a value.
 You can reference parameters in the `query` by a `$`, followed by the parameter name, for example, `$user`. Each such reference in the search query to a parameter name is substituted by the corresponding parameter value. For example, with parameter definition `PARAMS 4 lon 29.69465 lat 34.95126`, the expression `@loc:[$lon $lat 10 km]` is evaluated to `@loc:[29.69465 34.95126 10 km]`. You cannot reference parameters in the query string where concrete values are not allowed, such as in field names, for example, `@loc`. To use `PARAMS`, set `DIALECT` to `2` or greater than `2`.
 </details>
 
-<details open>
-<summary><code>ADDSCORES</code></summary>
-
-The `ADDSCORES` option exposes the full-text score values to the aggregation pipeline.
-You can use `@__score` in a pipeline as shown in the following example:
-
-`FT.AGGREGATE idx 'hello' ADDSCORES SORTBY 2 @__score DESC`
-</details>
-
 <details open>
 <summary><code>DIALECT {dialect_version}</code></summary> 
 

content/commands/ft.aggregate/index.md

@@ -20,7 +20,7 @@ You have two choices of Java clients that you can use with Redis:
 
 -   [Jedis]({{< relref "/develop/connect/clients/java/jedis" >}}), for synchronous applications.
 -   [Lettuce]({{< relref "/develop/connect/clients/java/lettuce" >}}),
-    for synchronous, asynchronous, and reactive applications.
+    for asynchronous and reactive applications.
 
 You can also access Redis with an object-mapping client interface. See
 [RedisOM for Java]({{< relref "/integrate/redisom-for-java" >}})

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

@@ -15,9 +15,9 @@ title: Jedis guide
 weight: 1
 ---
 
-[Jedis](https://github.com/redis/jedis) is a synchronous Java client for Redis.
+[Jedis](https://github.com/redis/jedis) is the *synchronous* Java client for Redis.
 Use [Lettuce]({{< relref "/develop/connect/clients/java/lettuce" >}}) if you need
-a more advanced Java client that also supports asynchronous and reactive connections.
+an *asynchronous* Java client.
 The sections below explain how to install `Jedis` and connect your application
 to a Redis database.
 

content/develop/connect/clients/java/jedis.md

@@ -15,11 +15,9 @@ title: Lettuce guide
 weight: 2
 ---
 
-[Lettuce](https://github.com/redis/lettuce/tree/main/src/main) is an advanced Java client for Redis
-that supports synchronous, asynchronous, and reactive connections.
-If you only need synchronous connections then you may find the other Java client
-[Jedis]({{< relref "/develop/connect/clients/java/jedis" >}}) easier to use.
-
+[Lettuce](https://github.com/redis/lettuce/tree/main/src/main) is the *asynchronous* Java client for Redis.
+Use [Jedis]({{< relref "/develop/connect/clients/java/jedis" >}}) if you need
+a *synchronous* Java client.
 The sections below explain how to install `Lettuce` and connect your application
 to a Redis database.
 
@@ -96,7 +94,7 @@ public class Async {
 }
 ```
 
-Learn more about asynchronous Lettuce API in [the reference guide](https://redis.github.io/lettuce/#asynchronous-api).
+Learn more about asynchronous Lettuce API in [the reference guide](https://lettuce.io/core/release/reference/index.html#asynchronous-api).
 
 ### Reactive connection
 
@@ -138,7 +136,7 @@ public class Main {
 }
 ```
 
-Learn more about reactive Lettuce API in [the reference guide](https://redis.github.io/lettuce/#reactive-api).
+Learn more about reactive Lettuce API in [the reference guide](https://lettuce.io/core/release/reference/index.html#reactive-api).
 
 ### Redis Cluster connection
 
@@ -180,15 +178,14 @@ RedisClient client = RedisClient.create(redisUri);
 Lettuce uses `ClientResources` for efficient management of shared resources like event loop groups and thread pools.
 For connection pooling, Lettuce leverages `RedisClient` or `RedisClusterClient`, which can handle multiple concurrent connections efficiently.
 
-### Timeouts
-
+### Timouts
 Lettuce provides timeouts for many operations, such as command execution, SSL handshake, and Sentinel discovery. By default, Lettuce uses a global timeout value of 60 seconds for these operations, but you can override the global timeout value with individual timeout values for each operation.
 
 {{% alert title="Tip" color="warning" %}}
 Choosing suitable timeout values is crucial for your application's performance and stability and is specific to each environment.
 Configuring timeouts is only necessary if you have issues with the default values. 
 In some cases, the defaults are based on environment-specific settings (e.g., operating system settings), while in other cases, they are built into the Lettuce driver. 
-For more details on setting specific timeouts, see the [Lettuce reference guide](https://redis.github.io/lettuce/).
+For more details on setting specific timeouts, see the [Lettuce reference guide](https://lettuce.io/core/release/reference/index.html).
 {{% /alert  %}}
 
 Below is an example of setting socket-level timeouts. The `TCP_USER_TIMEOUT` setting is useful for scenarios where the server stops responding without acknowledging the last request, while the `KEEPALIVE` setting is good for detecting dead connections where there is no traffic between the client and the server.
@@ -231,7 +228,6 @@ try (RedisClient client = RedisClient.create(redisURI)) {
 ```
 
 ### Connection pooling
-
 A typical approach with Lettuce is to create a single `RedisClient` instance and reuse it to establish connections to your Redis server(s).
 These connections are multiplexed; that is, multiple commands can be run concurrently over a single or a small set of connections, making explicit pooling less practical.
 
@@ -304,6 +300,6 @@ java.security.Security.setProperty("networkaddress.cache.negative.ttl", "0");
 
 ## Learn more
 
-- [Lettuce reference documentation](https://redis.github.io/lettuce/)
+- [Lettuce reference documentation](https://lettuce.io/docs/)
 - [Redis commands]({{< relref "/commands" >}})
 - [Project Reactor](https://projectreactor.io/)

content/develop/connect/clients/java/lettuce.md

@@ -144,47 +144,45 @@ Consider a hash data set for storing sensor data that has the following structur
 ```python
 event = {
     'air_quality': 256,
-    'battery_level':89
+    'Battery_level':89
 }
 
-r.hset('sensor:sensor1', mapping=event)
+client.hset('sensor:sensor1', mapping=event)
 ```
 
-In the examples below, you will likely need to refresh the `sensor:sensor1` key after its fields expire.
-
 Set and retrieve the TTL for multiple fields in a hash:
 
 ```python
 # set the TTL for two hash fields to 60 seconds
-r.hexpire('sensor:sensor1', 60, 'air_quality', 'battery_level')
-ttl = r.httl('sensor:sensor1', 'air_quality', 'battery_level')
+client.hexpire('sensor:sensor1', 60, 'air_quality', 'battery_level')
+ttl = client.httl('sensor:sensor1', 'air_quality', 'battery_level')
 print(ttl)
-# prints [60, 60]
+# prints [60]
 ```
 
 Set and retrieve a hash field's TTL in milliseconds:
 
 ```python
 # set the TTL of the 'air_quality' field in milliseconds
-r.hpexpire('sensor:sensor1', 60000, 'air_quality')
+client.hpexpire('sensor:sensor1', 60000, 'air_quality')
 # and retrieve it
-pttl = r.hpttl('sensor:sensor1', 'air_quality')
+pttl = client.hpttl('sensor:sensor1', 'air_quality')
 print(pttl)
-# prints [59994] # your actual value may vary
+# prints [60000]
 ```
 
 Set and retrieve a hash field’s expiration timestamp:
 
 ```python
 # set the expiration of 'air_quality' to now + 24 hours
 # (similar to setting the TTL to 24 hours)
-r.hexpireat('sensor:sensor1', 
+client.hexpireat('sensor:sensor1', 
     datetime.now() + timedelta(hours=24), 
     'air_quality')
 # and retrieve it
-expire_time = r.hexpiretime('sensor:sensor1', 'air_quality')
+expire_time = client.hexpiretime('sensor:sensor1', 'air_quality')
 print(expire_time)
-# prints [1717668041] # your actual value may vary
+# prints [1717668041]
 ```
 
 ## Performance

content/develop/data-types/hashes.md

@@ -1,6 +1,6 @@
 ### Migration guides for certain clients
 
-If you are using [Go-Redis](https://redis.uptrace.dev/) v9 or [Lettuce](https://redis.github.io/lettuce/) v6+, which by default switch to the RESP3 protocol, and you are running Redis Stack commands, please make sure the protocol version is pinned to RESP2 prior to upgrading to Redis version 7.2.
+If you are using [Go-Redis](https://redis.uptrace.dev/) v9 or [Lettuce](https://lettuce.io/) v6+, which by default switch to the RESP3 protocol, and you are running Redis Stack commands, please make sure the protocol version is pinned to RESP2 prior to upgrading to Redis version 7.2.
 
 #### Go-Redis
 

content/embeds/r7.2-migration-guides.md

@@ -2,7 +2,7 @@ Before creating a Redis Cloud database, you need to [create an account]({{< relr
 
 To create a database in your Redis Cloud account:
 
-1. Sign in to the [Redis Cloud console](https://cloud.redis.io).
+1. Sign in to the [Redis Cloud console](https://app.redislabs.com).
 
 2. Select the **New database** button.
 

content/embeds/rc-create-db-first-steps.md

@@ -9,12 +9,12 @@ Redis is an [in-memory data store]({{< relref "/develop/get-started/data-store"
 
 You can install Redis from source, from an executable for your OS, or bundled with Redis Stack and Redis Insight which include popular features and monitoring.
 
+* [Install Redis from Source]({{< relref "/operate/oss_and_stack/install/install-redis/install-redis-from-source" >}})
 * [Install Redis on Linux]({{< relref "/operate/oss_and_stack/install/install-redis/install-redis-on-linux" >}})
 * [Install Redis on macOS]({{< relref "/operate/oss_and_stack/install/install-redis/install-redis-on-mac-os" >}})
 * [Install Redis on Windows]({{< relref "/operate/oss_and_stack/install/install-redis/install-redis-on-windows" >}})
 * [Install Redis with Redis Stack and Redis Insight]({{< relref "/operate/oss_and_stack/install/install-stack" >}})
 * [Run Redis Stack on Docker]({{< relref "/operate/oss_and_stack/install/install-stack/docker" >}})
-* [Install Redis from Source]({{< relref "/operate/oss_and_stack/install/install-redis/install-redis-from-source" >}})
 
 ## Use cases