Skip to content

Commit 0eea90a

Browse files
Merge pull request #1549 from redis/DOC-5223-rdi-rel-notes-v180
DOC-5223 RDI release notes for v1.8.0
2 parents 46fbda4 + 3c1d34a commit 0eea90a

File tree

6 files changed

+100
-10
lines changed

6 files changed

+100
-10
lines changed

config.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ rdi_redis_gears_version = "1.2.6"
5555
rdi_debezium_server_version = "2.3.0.Final"
5656
rdi_db_types = "cassandra|mysql|oracle|postgresql|sqlserver"
5757
rdi_cli_latest = "latest"
58-
rdi_current_version = "v1.6.7"
58+
rdi_current_version = "1.8.0"
5959

6060
[params.clientsConfig]
6161
"Python"={quickstartSlug="redis-py"}

content/integrate/redis-data-integration/installation/install-k8s.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,10 +54,10 @@ Complete the following steps before installing the RDI Helm chart:
5454
more information).
5555

5656
- Download the RDI Helm chart tar file from the
57-
[Redis download center](https://redis.io/downloads/) (in the *Modules, Tools & Integration* category) .
57+
[Redis download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-{{< rdi-version >}}.tgz) (in the *Modules, Tools & Integration* category) .
5858

5959
```bash
60-
export RDI_VERSION=<version>
60+
export RDI_VERSION={{< rdi-version >}}
6161
wget https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-$RDI_VERSION.tgz
6262
```
6363

content/integrate/redis-data-integration/installation/install-vm.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ This guide explains how to install Redis Data Integration (RDI) on one or more V
2020
your source database. You can also
2121
[Install RDI on Kubernetes]({{< relref "/integrate/redis-data-integration/installation/install-k8s" >}}).
2222

23-
{{< note >}}We recommend you always use the latest version, which is RDI {{< field "rdi_current_version" >}}.
23+
{{< note >}}We recommend you always use the latest version, which is RDI v{{< rdi-version >}}.
2424
{{< /note >}}
2525

2626
## Create the RDI database
@@ -137,12 +137,12 @@ sudo ufw reload
137137
Follow the steps below for each of your VMs:
138138

139139
1. Download the RDI installer from the
140-
[Redis download center](https://redis.io/downloads/)
140+
[Redis download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-installation-{{< rdi-version >}}.tar.gz)
141141
(from the *Modules, Tools & Integration* category) and extract it to your preferred installation
142142
folder.
143143

144144
```bash
145-
export RDI_VERSION=<version>
145+
export RDI_VERSION={{< rdi-version >}}
146146
wget https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-installation-$RDI_VERSION.tar.gz
147147
tar -xvf rdi-installation-$RDI_VERSION.tar.gz
148148
```

content/integrate/redis-data-integration/installation/upgrade.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,12 +22,12 @@ Follow the steps below to upgrade an existing
2222
[VM installation]({{< relref "/integrate/redis-data-integration/installation/install-vm" >}})
2323
of RDI:
2424

25-
1. Download the RDI installer from the [Redis download center](https://redis.io/downloads/)
25+
1. Download the RDI installer from the [Redis download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-installation-{{< rdi-version >}}.tar.gz)
2626
(in the *Modules, Tools & Integration* category) and extract it to your
2727
preferred installation folder.
2828

2929
```bash
30-
export RDI_VERSION=<version>
30+
export RDI_VERSION={{< rdi-version >}}
3131
wget https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-installation-$RDI_VERSION.tar.gz
3232
tar -xvf rdi-installation-$RDI_VERSION.tar.gz
3333
```
@@ -92,11 +92,11 @@ installation of RDI:
9292
[Using a private image registry]({{< relref "/integrate/redis-data-integration/installation/install-k8s#using-a-private-image-registry" >}})
9393
and add them to your local registry.
9494

95-
1. Download the RDI Helm chart tar file from the [Redis download center](https://redis.io/downloads/)
95+
1. Download the RDI Helm chart tar file from the [Redis download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-{{< rdi-version >}}.tgz)
9696
(in the *Modules, Tools & Integration* category).
9797

9898
```bash
99-
export RDI_VERSION=<version>
99+
export RDI_VERSION={{< rdi-version >}}
100100
wget https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-$RDI_VERSION.tgz
101101
```
102102

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
---
2+
Title: Redis Data Integration release notes 1.8.0 (May 2025)
3+
alwaysopen: false
4+
categories:
5+
- docs
6+
- operate
7+
- rs
8+
description: |
9+
Enhanced RDI operator for better pipeline orchestration, resiliency, observability and flexibility;
10+
External collector support;
11+
Labels and annotations to RDI data plane pods;
12+
Custom Debezium image;
13+
Calculated TTL for target database.
14+
linkTitle: 1.8.0 (May 2025)
15+
toc: 'true'
16+
weight: 984
17+
---
18+
19+
{{< note >}}This minor release replaces the 1.6.7 release.{{< /note >}}
20+
21+
RDI’s mission is to help Redis customers sync Redis Enterprise with live data from their slow disk-based databases to:
22+
23+
- Meet the required speed and scale of read queries and provide an excellent and predictable user experience.
24+
- Save resources and time when building pipelines and coding data transformations.
25+
- Reduce the total cost of ownership by saving money on expensive database read replicas.
26+
27+
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.
28+
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.
29+
30+
## Headlines
31+
32+
- Enhanced RDI operator for better pipeline orchestration, resiliency, observability, and flexibility. It
33+
will also enable many new features in the near future.
34+
- You can now use an external collector that is not managed by RDI but writes into RDI streams
35+
(Debezium compatible).
36+
- You can now add labels and annotations to RDI data plane pods, for example to control service
37+
mesh features.
38+
- RDI now uses a custom image of Debezium (based on `3.0.8.Final`) to address known vulnerabilities.
39+
- Added support for calculated TTL for target database keys via `expire` expressions.
40+
41+
## Detailed changes
42+
43+
### Helm chart changes
44+
45+
- All collector and processor values that were previously under `collector`, `collectorSourceMetricsExporter`, and `processor` have been moved to `operator.dataPlane.collector` and `operator.dataPlane.processor`.
46+
- `global.collectorApiEnabled` has been moved to `operator.dataPlane.collectorApi.enabled`, and is now a boolean value (`true` or `false`), not `"0"` or `"1"`.
47+
- `api.authEnabled` is also now a boolean value, not `"0"` or `"1"`.
48+
- The following values have been deprecated: `rdiMetricsExporter.service.protocol`, `rdiMetricsExporter.service.port`, `rdiMetricsExporter.serviceMonitor.path`, `api.service.name`
49+
- You can now add custom labels and annotations to all RDI components.
50+
- You can now disable the creation of the RDI system secrets.
51+
52+
### Operator Improvements
53+
54+
The RDI operator has been significantly enhanced in the following areas:
55+
56+
- **Resilience**: The operator now always maintains the desired pipeline state. Manual changes or random disruptions are reverted automatically.
57+
- **Automatic recovery**: When a configuration issue is resolved, the entire pipeline starts automatically, eliminating the need for manual redeployment.
58+
- **Consistency**: A pipeline that has been stopped with `stop` will remain stopped after `deploy` or `reset`, until explicitly started again.
59+
- **Enhanced configuration**: You can now configure data plane components in ways that were previously not supported, such as adding labels and annotations.
60+
- **External collector support**: No collector resources are created for sources of type `external`.
61+
- **Enhanced troubleshooting**: You can now gain extra insight into the pipeline state by examining the `Pipeline` and `PipelineRelease` custom K8s resources.
62+
63+
### Other Features, Improvements and Enhancements
64+
65+
- Added `expire` expression for target output in transformation jobs.
66+
- Addressed security vulnerabilities: TLS certificate hostname verification is now ON by default.
67+
- Improved Helm default values while preserving `values.yaml` formatting.
68+
- Enhanced Helm values and templates for better configuration.
69+
- Added a script to create or update secrets when using Helm (`rdi-secret.sh` in the Helm zip file).
70+
- Improved validation schema and ensured backward compatibility.
71+
- Fixed compatibility issues with newer versions of `requests` and `urllib3`.
72+
- Improved error messages for JSON schema validation.
73+
- Improved PostgreSQL documentation for mTLS.
74+
- Added timestamps to the `status` command.
75+
- Fixed issues with `primary_key` and `unique_constraint` attributes in Oracle metadata.
76+
- Added `capture.mode` to MongoDB scaffolding.
77+
- Improved Helm TLS setup for RDI database connections.
78+
- Enhanced error handling and validation for transformation jobs.
79+
- Improved documentation for supported platforms and configurations.
80+
81+
### Fixes
82+
83+
- Fixed HTTP 500 error when querying columns with tables parameter.
84+
- Improved Helm TLS setup for RDI database connections.
85+
- Fixed keystore overwrite when using mTLS on both source and RDI DBs in the collector.
86+
87+
## Limitations
88+
89+
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.

layouts/shortcodes/rdi-version.html

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{{- .Site.Params.rdi_current_version -}}

0 commit comments

Comments
 (0)