You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
+
- Update documentation on pipelines endpoint.
33
+
- Fix deploy pipeline validation issues.
34
+
-`/tables` API now groups tables by schema if supported; otherwise, by database catalog.
35
+
- Fix mongo tables endpoint.
36
+
- Fix Oracle `/metadata` and `/columns` filters being case sensitive.
37
+
38
+
## Limitations
39
+
40
+
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