---
Title: Redis Data Integration release notes 1.12.1 (June 2025)
alwaysopen: false
categories:
- docs
- operate
- rs
description: |
    Update documentation on pipelines endpoint.
    Fix deploy pipeline validation issues.
    /tables API can now group tables by schema.
    Fix mongo tables endpoint.
    Fix Oracle /metadata and /columns filters being case sensitive.
linkTitle: 1.12.1 (June 2025)
toc: 'true'
weight: 981
---

{{< note >}}This maintenance release replaces the 1.12.0 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.

## Headlines

- Update documentation on pipelines endpoint.
- Fix deploy pipeline validation issues.
- `/tables` API now groups tables by schema if supported; otherwise, by database catalog.
- Fix mongo tables endpoint.
- Fix Oracle `/metadata` and `/columns` filters being case sensitive.

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