RDI 1.16.2 Release

content/embeds/rdi-db-reqs.md

@@ -34,6 +34,8 @@
     -H "Content-Type: application/json" \
     -X PUT https://<CLUSTER_FQDN>:9443/v1/bdbs/<BDB_UID>
   ```
+ If you don't have permissions to use AOF persistence, please check the [Using RDI without persistence]({{< relref "/integrate/redis-data-integration/faq#can-i-use-rdi-without-persistence-enabled" >}}) section in the FAQ.
+
 * **Ensure that the RDI database is not clustered.** RDI will not work correctly if the
   RDI database is clustered (but note that the target database *can* be clustered without
   any problems).

content/integrate/redis-data-integration/faq.md

@@ -86,3 +86,18 @@ queue is stored as a capped stream in the RDI staging database. You can see its
 with Redis Insight or with the 
 [`redis-di get-rejected`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-get-rejected" >}})
 command from the CLI.
+
+
+## Can I use RDI without persistence enabled?
+
+By default, RDI requires persistence to be enabled on the RDI database. This ensures that RDI can recover both its configuration and the last known state if the cluster crashes.
+
+If you don't have permissions to use persistence due to compliance or other reasons, you can disable
+the persistence check on the RDI database (Helm installation only). If you do this, RDI will not be 
+able to recover from a crash, and you will have to perform a new deploy to reinitialize the pipeline.
+
+To disable the persistence check, set the `aofRequired` value to `false` in the `operator->prerequisiteChecks`
+section of the `values.yaml` file.
+
+This option is available in RDI 1.16.2 and later.
+

content/integrate/redis-data-integration/release-notes/rdi-1-16-2.md

@@ -0,0 +1,33 @@
+---
+Title: Redis Data Integration release notes 1.16.2 (March 2026)
+alwaysopen: false
+categories:
+- docs
+- operate
+- rs
+description: |
+  Maintenance release focusing on allowing the use of RDI with Redis Enterprise databases that have AOF disabled.
+linkTitle: 1.16.2 (March 2026)
+toc: 'true'
+weight: 972
+---
+
+{{< note >}}This maintenance release replaces the 1.16.1 release.{{< /note >}}
+
+RDI's mission is to help Redis customers sync Redis Enterprise with live data from their slow disk-based databases to:
+
+- Meet the required speed and scale of read queries and provide an excellent and predictable user experience.
+- Save resources and time when building pipelines and coding data transformations.
+- Reduce the total cost of ownership by saving money on expensive database read replicas.
+
+RDI keeps the Redis cache up to date with changes in the primary database, using a [_Change Data Capture (CDC)_](https://en.wikipedia.org/wiki/Change_data_capture) mechanism.
+It also lets you _transform_ the data from relational tables into convenient and fast data structures that match your app's requirements. You specify the transformations using a configuration system, so no coding is required.
+
+## What's New in 1.16.2
+
+- **New configuration option to disable AOF check:** A new prerequisiteChecks section is introduced in the operator section of the Helm values file. You can use it to disable the AOF prerequisite check when running RDI against a Redis RDI database that does not have AOF enabled. Please note that disabling this check without understanding the implications may lead to data loss in certain failure scenarios, so it should be used with caution.
+
+## Limitations
+
+RDI can write data to a Redis Active-Active database. However, it doesn't support writing data to two or more Active-Active replicas. Writing data from RDI to several Active-Active replicas could easily harm data integrity as RDI is not synchronous with the source database commits.
+