|
| 1 | +--- |
| 2 | +Title: Redis Data Integration release notes 1.15.1 (November 2025) |
| 3 | +alwaysopen: false |
| 4 | +categories: |
| 5 | +- docs |
| 6 | +- operate |
| 7 | +- rs |
| 8 | +description: | |
| 9 | + Fixes support package generation and masking to simplify troubleshooting and log collection. |
| 10 | + Improves processor throughput during initial sync via parallel processing and new stream tuning parameters. |
| 11 | + Adds an advanced configuration option to pass custom Java options to the Debezium collector. |
| 12 | +linkTitle: 1.15.1 (November 2025) |
| 13 | +toc: 'true' |
| 14 | +weight: 975 |
| 15 | +--- |
| 16 | + |
| 17 | +{{< note >}}This maintenance release replaces the 1.15.0 release.{{< /note >}} |
| 18 | + |
| 19 | +RDI’s mission is to help Redis customers sync Redis Enterprise with live data from their slow disk-based databases to: |
| 20 | + |
| 21 | +- Meet the required speed and scale of read queries and provide an excellent and predictable user experience. |
| 22 | +- Save resources and time when building pipelines and coding data transformations. |
| 23 | +- Reduce the total cost of ownership by saving money on expensive database read replicas. |
| 24 | + |
| 25 | +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. |
| 26 | +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. |
| 27 | + |
| 28 | +## What's New in 1.15.1 |
| 29 | + |
| 30 | +- Fix dump support package problems |
| 31 | + - Fix improper namespace passing to the kubectl command |
| 32 | + - Mask passwords from sensitive configs |
| 33 | + - Dump masked pipeline information |
| 34 | + - Mask and dump audit logs collected from RDI DB rdi:tasks streams |
| 35 | +- Processor performance improvements - Increase throughput during initial snapshot by ~50% during initial sync |
| 36 | + - Added parameter - `read_batch_timeout_ms` to the processor configuration to control the timeout for reading from the RDI streams. The default is 100ms. |
| 37 | + - `read_batch_size` is now functional. In previous versions, the processor would always read a batch size of 2000 from the stream, regardless of the `read_batch_size` value. |
| 38 | +- Added parameter `sources.advanced.java_options` to the `config.yaml` file to pass additional options to the Debezium collector command line e.g. increasing heap size. |
| 39 | + |
| 40 | +## Limitations |
| 41 | + |
| 42 | +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. |
0 commit comments