Merge branch 'main' into DOC-4137

Author: cmilesb

.github/workflows/redis_modules_docs_sync.yaml

@@ -0,0 +1,84 @@
+name: redis_modules_docs_sync
+
+on:
+  schedule:
+    - cron: '0 0 * * *' # run every day at midnight UTC time
+  workflow_dispatch: # or run on manual trigger
+
+jobs:
+  redis_modules_docs_sync:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      actions: write
+    steps:
+      - name: 'Checkout'
+        uses: 'actions/checkout@v3'
+
+      - name: 'Fetch commands json files from modules'
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          branch="redis_modules_docs_sync"
+          modules_list=("redisjson" "redisbloom" "redistimeseries" "redisearch")
+          module_change=false
+
+          # check if remote branch already exists
+          git fetch --all
+          set +e
+          git ls-remote --exit-code --heads origin "refs/heads/${branch}"
+          if [ "$?" -eq 0 ]; then
+            set -e
+            # if it does, create local branch off existing remote branch
+            git checkout -b "${branch}" "origin/${branch}"
+            git branch --set-upstream-to="origin/${branch}" "${branch}"
+            git pull
+          else
+            set -e
+            # otherwise, create local branch from main
+            git checkout -b "${branch}"
+          fi
+
+          for module in "${modules_list[@]}"; do
+            # Find latest version
+            module_version=$(
+              curl -Ls \
+              -H "Accept: application/vnd.github+json" \
+              -H "Authorization: Bearer ${GH_TOKEN}" \
+              -H "X-GitHub-Api-Version: 2022-11-28" \
+              "https://api.github.com/repos/${module}/${module}/releases/latest" \
+              | jq -r '.tag_name'
+            )
+
+            # Fetch release
+            gh release download "$module_version" -R "${module}/${module}" -A zip -O "${module}.zip"
+            unzip "${module}.zip" -d "${module}"
+            cp ${module}/*/commands.json "data/commands_${module}.json"
+
+            modules_commands_is_different=$(git diff "data/commands_${module}.json")
+            if [[ ! -z $modules_commands_is_different ]]; then
+              module_change=true
+              
+              git add "data/commands_${module}.json"
+              git config user.email "177626021+redisdocsapp[bot]@users.noreply.github.com"
+              git config user.name "redisdocsapp[bot]"
+              git commit -m "Update data/commands_${module}.json for release ${module_version}"
+            fi
+          done
+
+          if [ "$module_change" = true ] ; then
+            git push origin "${branch}"
+
+            # If a pr is not already open, create one
+            set +e
+            gh search prs -R redis/docs --state open --match title "redis modules docs sync" | grep -q "redis modules docs sync"
+            if [ "$?" -eq 1 ]; then
+              set -e
+              gh pr create \
+                --body "redis modules docs sync" \
+                --title "redis modules docs sync" \
+                --head "$branch" \
+                --base "main"
+            fi
+          fi

content/develop/connect/clients/_index.md

@@ -39,10 +39,11 @@ Redis does not support directly:
 | Language | Client name | Github | Docs |
 | :-- | :-- | :-- | :-- |
 | C | hiredis | https://github.com/redis/hiredis | https://github.com/redis/hiredis |
-| [PHP](https://www.php.net/) | redis extension | https://github.com/phpredis/phpredis | https://github.com/phpredis/phpredis/blob/develop/README.md |
-| [PHP](https://www.php.net/) | predis library | https://github.com/predis/predis | https://github.com/predis/predis/wiki |
+| [PHP](https://www.php.net/) | PhpRedis extension | https://github.com/phpredis/phpredis | https://github.com/phpredis/phpredis/blob/develop/README.md |
+| [PHP](https://www.php.net/) | Predis library | https://github.com/predis/predis | https://github.com/predis/predis/wiki |
 | [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/ | 
+| [Rust](https://www.rust-lang.org/) | redis-rs | https://github.com/redis-rs/redis-rs | https://docs.rs/redis/latest/redis/ |
+| [C++](https://en.wikipedia.org/wiki/C%2B%2B) | Boost.Redis | https://github.com/boostorg/redis | https://www.boost.org/doc/libs/develop/libs/redis/doc/html/index.html |
 
 ## Requirements
 

content/develop/reference/protocol-spec.md

@@ -537,20 +537,22 @@ The first element is a key, followed by the corresponding value, then the next k
 
 The attribute type is exactly like the Map type, but instead of a `%` character as the first byte, the `|` character is used. Attributes describe a dictionary exactly like the Map type. However the client should not consider such a dictionary part of the reply, but as auxiliary data that augments the reply.
 
+Note: in the examples below, indentation is shown only for clarity; the additional whitespace would not be part of a real reply.
+
 For example, newer versions of Redis may include the ability to report the popularity of keys for every executed command. The reply to the command `MGET a b` may be the following:
 
-    |1<CR><LF>
-        +key-popularity<CR><LF>
-        %2<CR><LF>
-            $1<CR><LF>
-            a<CR><LF>
-            ,0.1923<CR><LF>
-            $1<CR><LF>
-            b<CR><LF>
-            ,0.0012<CR><LF>
-    *2<CR><LF>
-        :2039123<CR><LF>
-        :9543892<CR><LF>
+    |1\r\n
+        +key-popularity\r\n
+        %2\r\n
+            $1\r\n
+            a\r\n
+            ,0.1923\r\n
+            $1\r\n
+            b\r\n
+            ,0.0012\r\n
+    *2\r\n
+        :2039123\r\n
+        :9543892\r\n
 
 The actual reply to `MGET` is just the two item array `[2039123, 9543892]`. The returned attributes specify the popularity, or frequency of requests, given as floating point numbers ranging from `0.0` to `1.0`, of the keys mentioned in the original command. Note: the actual implementation in Redis may differ.
 
@@ -569,13 +571,13 @@ When a client reads a reply and encounters an attribute type, it should read the
 
 Attributes can appear anywhere before a valid part of the protocol identifying a given type, and supply information only about the part of the reply that immediately follows. For example:
 
-    *3<CR><LF>
-        :1<CR><LF>
-        :2<CR><LF>
-        |1<CR><LF>
-            +ttl
-            :3600
-        :3<CR><LF>
+    *3\r\n
+        :1\r\n
+        :2\r\n
+        |1\r\n
+            +ttl\r\n
+            :3600\r\n
+        :3\r\n
 
 In the above example the third element of the array has associated auxiliary information of `{ttl:3600}`. Note that it's not up to the client library to interpret the attributes, but it should pass them to the caller in a sensible way.
 

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-string-example.md

@@ -0,0 +1,52 @@
+---
+Title: Write to a Redis string
+aliases: null
+alwaysopen: false
+categories:
+- docs
+- integrate
+- rs
+- rdi
+description: null
+group: di
+linkTitle: Write to a Redis string
+summary: Redis Data Integration keeps Redis in sync with the primary database in near
+  real time.
+type: integration
+weight: 30
+---
+
+The string data type is useful for capturing a string representation of a single column from
+a source table.
+
+In the example job below, the `title` column is captured from the `invoice` table in the source.
+The `title` is then written to the Redis target database as a string under a custom key of the
+form `AlbumTitle:42`, where the `42` is the primary key value of the table (the `albumid` column).
+
+The `connection` is an optional parameter that refers to the corresponding connection name defined in
+[`config.yaml`]({{< relref "integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}}). 
+When you specify the `data_type` parameter for the job, it overrides the system-wide setting `target_data_type` defined in `config.yaml`. Here, the `string` data type also requires an `args` subsection
+with a `value` argument that specifies the column you want to capture from the source table.
+
+The optional `expire` parameter sets the length of time, in seconds, that a new key will
+persist for after it is created (here, it is 86400 seconds, which equals one day).
+After this time, the key will be deleted automatically.
+If you don't supply an `expire` parameter, the keys will never expire. 
+
+```yaml
+source:
+  server_name: chinook
+  table: album
+  row_format: full
+output:
+  - uses: redis.write
+    with:
+      connection: target
+      data_type: string
+      key:
+        expression: concat(['AlbumTitle:', values(key)[0]])
+        language: jmespath
+      args:
+        value: title
+      expire: 86400
+```

content/integrate/write-behind/data-transformation/data-transformation-pipeline.md

@@ -32,7 +32,7 @@ For example, the default job can streamline tasks such as adding a prefix or pos
 Currently, the default job is supported for ingest pipelines only.
 
 ### Example
-This example demonstrates the process of adding an `app_code` field with a value of `foo` using the [add_field]({{<relref "/content/rdi/reference/data-transformation-block-types/add_field/">}}) block to all tables that lack explicitly defined jobs. Additionally, it appends an `aws` prefix and a `gcp` postfix to every generated hash key.
+This example demonstrates the process of adding an `app_code` field with a value of `foo` using the [add_field]({{<relref "/integrate/write-behind/reference/data-transformation-block-types/add_field">}}) block to all tables that lack explicitly defined jobs. Additionally, it appends an `aws` prefix and a `gcp` postfix to every generated hash key.
 
 default.yaml
 ```yaml

content/operate/kubernetes/deployment/deployment-options.md

@@ -15,8 +15,10 @@ You can deploy Redis Enterprise for Kubernetes in several different ways dependi
 
 Multiple Redis Enterprise database resources (REDB) can be associated with single Redis Enterprise cluster resource (REC) even if they reside in different namespaces.
 
-{{<note>}} The Redis Enterprise cluster (REC) custom resource must reside in the same namespace as the Redis Enterprise operator.
-{{</note>}}
+The Redis Enterprise cluster (REC) custom resource must reside in the same namespace as the Redis Enterprise operator.
+
+{{<warning>}} Multi-namespace installations don't support Active-Active databases (REEADB). Only databases created with the REDB resource are supported in multi-namespace deployments at this time.{{</warning>}}
+
 
 ## Single REC and single namespace (one-to-one)
 

content/operate/kubernetes/re-clusters/multi-namespace.md

@@ -16,6 +16,8 @@ Multiple Redis Enterprise database resources (REDBs) can be associated with a si
 
 To learn more about designing a multi-namespace Redis Enterprise cluster, see [flexible deployment options]({{< relref "/operate/kubernetes/deployment/deployment-options.md" >}}).
 
+{{<warning>}} Multi-namespace installations don't support Active-Active databases (REEADB). Only databases created with the REDB resource are supported in multi-namespace deployments at this time.{{</warning>}}
+
 ## Prerequisites
 
 Before configuring a multi-namespace deployment, you must have a running [Redis Enterprise cluster (REC)]({{< relref "/operate/kubernetes/deployment/quick-start.md" >}}). See more information in the [deployment]({{< relref "/operate/kubernetes/deployment/" >}}) section.

content/operate/kubernetes/release-notes/6-2-18-releases/k8s-6-2-18-3.md

@@ -171,4 +171,4 @@ On clusters with more than 9 REC nodes, a Kubernetes upgrade can render the Redi
 
 ## Security
 
-For a list of fixes related to CVEs, see the [Redis Enterprise 6.2.18-58 release notes]({{<relref "operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-58/#security">}}).
+For a list of fixes related to CVEs, see the [Redis Enterprise 6.2.18-58 release notes]({{<relref "operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-58#security">}}).

content/operate/kubernetes/release-notes/6-2-18-releases/k8s-6-2-18-41-jan-2023.md

@@ -60,4 +60,4 @@ See [Redis Enterprise for Kubernetes release notes 6.2.18-41 (Dec 2022)]({{< rel
 
 ## Security
 
-For a list of fixes related to CVEs, see the [Redis Enterprise 6.2.18-72 release notes]({{<relref "operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-72/#security">}}).
+For a list of fixes related to CVEs, see the [Redis Enterprise 6.2.18-72 release notes]({{<relref "operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-70#security">}}).

content/operate/kubernetes/release-notes/6-2-18-releases/k8s-6-2-18-41.md

@@ -141,4 +141,4 @@ On clusters with more than 9 REC nodes, a Kubernetes upgrade can render the Redi
 
 ## Security
 
-For a list of fixes related to CVEs, see the [Redis Enterprise 6.2.18-65 release notes]({{<relref "operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-65/#security">}}).
+For a list of fixes related to CVEs, see the [Redis Enterprise 6.2.18-65 release notes]({{<relref "operate/rs/release-notes/rs-6-2-18-releases/rs-6-2-18-65#security">}}).