Redis Data Integration release notes 1.12.3 (July 2025)

Fixed operator excessive CPU usage and log flooding. Fixed reset jobs not being able to pull images from private registries.

Note:
This maintenance release replaces the 1.12.2 release.

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) 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.

Headlines

  • Fixed operator excessive CPU usage and log flooding caused by annotation conflict between PipelineRelease and Kubernetes deployment controllers.
  • Fixed reset jobs not being able to pull images from private registries due to missing image pull secrets.

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.

RATE THIS PAGE
Back to top ↑