{
  "schema_version": 2,
  "id": "integrate/redis-data-integration/release-notes/rdi-1-6-1",
  "title": "Redis Data Integration release notes 1.6.1 (March 2025)",
  "url": "https://redis.io/docs/latest/integrate/redis-data-integration/release-notes/rdi-1-6-1/",
  "summary": "Installation on Kubernetes with a Helm chart. Improvements for installation on VMs.",
  "tags": [
    "docs",
    "operate",
    "rs"
  ],
  "last_updated": "2026-09-18T16:47:10+01:00",
  "page_type": "content",
  "content_hash": "dbe62df6f64e7b916f0f3b9b551930982eb31f7826ade91ca62ef7e46b2f8e83",
  "sections": [
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "> This release replaces the 1.6.0 release.\n\nRDI’s mission is to help Redis customers sync Redis Enterprise with live data from their slow disk-based databases to:\n\n- Meet the required speed and scale of read queries and provide an excellent and predictable user experience.\n- Save resources and time when building pipelines and coding data transformations.\n- Reduce the total cost of ownership by saving money on expensive database read replicas.\n\nRDI 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.\nIt 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."
    },
    {
      "id": "headlines",
      "title": "Headlines",
      "role": "content",
      "text": "- Fixed missing metrics and incorrect status for SQL Server.\n- Improved Redis Insight autocomplete using schema description property.\n- Restricted Redis connections to targets and non-Redis connections to sources.\n- Enhanced scaffolded `config.yaml` with examples for each database type.\n- VM Installer: Captured output of all sub-processes.\n- Improved error message for critical errors when sending commands to Redis cluster fails.\n- Fixed issue where pipeline status did not return to streaming after stopping and starting.\n- Added RDI API logging, validation examples, and bug fixes.\n- Disabled strict parsing of collector application properties to allow overriding.\n- Fixed HTTP 500 error in `GET /pipelines/sources/{source}/columns` when passing tables parameter.\n- VM setup: Fixed incorrect output status and incomplete upgrades in `upgrade.sh` script.\n- Ensured `collector-api` service force upgrades when `Operator` restarts.\n- Corrected typos in CLI option help messages.\n- Generated and published [API reference page](https://redis.io/docs/latest/integrate/redis-data-integration/reference/api-reference).\n- Resolved error in `collector-api` when Source secret contains special characters.\n- Fixed RDI 1.6.0 installation failure for HA due to `rdi-operator` deployment timeout.\n- Added support for downloading Debezium image from a private registry.\n- VM Installer now supports Ubuntu 22.04 and Ubuntu 24.04.\n- Resolved performance degradation in 1.6.0 that caused the initial sync to be 3-5 times slower."
    },
    {
      "id": "limitations",
      "title": "Limitations",
      "role": "limits",
      "text": "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."
    }
  ],
  "examples": []
}