RDSC-5884: RDI 1.19.1 release notes - #3783
Open
ZdravkoDonev-redis wants to merge 4 commits into
Open
Conversation
Contributor
🧠 Redis MemoryFound 8 related items from repository history (1 new this commit):
Memory updated at bf91043 |
Contributor
andy-stark-redis
approved these changes
Aug 11, 2026
andy-stark-redis
left a comment
andy-stark-redis
left a comment
Contributor
There was a problem hiding this comment.
A few suggestions but basically looks OK so far. Also, I've updated the RDI version number in the config.
|
|
||
| ### New Features | ||
|
|
||
| - **Database-scoped pipeline secret keys**: Pipeline secrets in API v2 and the `redis-di` CLI now use database-independent keys (`USERNAME`, `PASSWORD`, `CACERT`, `CERT`, `KEY`, `KEY_PASSWORD`) together with a `db` parameter (`--db` in the CLI) that names the database the secret belongs to: a source name, or `target`. The previous scope-prefixed keys (`SOURCE_DB_*`, `TARGET_DB_*`) remain accepted for single-source and target secrets, used without the `db` parameter. |
Contributor
There was a problem hiding this comment.
Maybe a bit clearer?
Suggested change
| - **Database-scoped pipeline secret keys**: Pipeline secrets in API v2 and the `redis-di` CLI now use database-independent keys (`USERNAME`, `PASSWORD`, `CACERT`, `CERT`, `KEY`, `KEY_PASSWORD`) together with a `db` parameter (`--db` in the CLI) that names the database the secret belongs to: a source name, or `target`. The previous scope-prefixed keys (`SOURCE_DB_*`, `TARGET_DB_*`) remain accepted for single-source and target secrets, used without the `db` parameter. | |
| - **Database-scoped pipeline secret keys**: Pipeline secrets in API v2 and the `redis-di` CLI now use database-independent keys (`USERNAME`, `PASSWORD`, `CACERT`, `CERT`, `KEY`, `KEY_PASSWORD`) together with a `db` parameter (`--db` in the CLI) that names the database the secret belongs to: a source name, or `target`. The previous scope-prefixed keys (`SOURCE_DB_*`, `TARGET_DB_*`) are still accepted for single-source and target secrets when used without the `db` parameter. |
| ### New Features | ||
|
|
||
| - **Database-scoped pipeline secret keys**: Pipeline secrets in API v2 and the `redis-di` CLI now use database-independent keys (`USERNAME`, `PASSWORD`, `CACERT`, `CERT`, `KEY`, `KEY_PASSWORD`) together with a `db` parameter (`--db` in the CLI) that names the database the secret belongs to: a source name, or `target`. The previous scope-prefixed keys (`SOURCE_DB_*`, `TARGET_DB_*`) remain accepted for single-source and target secrets, used without the `db` parameter. | ||
| - **Richer validation errors from API v1 pipeline configuration endpoints**: A `422` response from `/pipelines/undeploy`, `/pipelines/sources/*`, `/pipelines/targets/*`, `/pipelines/processors/*`, and `/pipelines/secret-providers/*` may now include an `errors` array with structured per-field detail, in addition to the existing `detail` message, matching the shape already returned by `POST /pipelines` and `PATCH /pipelines`. Existing clients that only read `detail` are unaffected. |
Contributor
There was a problem hiding this comment.
Maybe break up the long sentence?
Suggested change
| - **Richer validation errors from API v1 pipeline configuration endpoints**: A `422` response from `/pipelines/undeploy`, `/pipelines/sources/*`, `/pipelines/targets/*`, `/pipelines/processors/*`, and `/pipelines/secret-providers/*` may now include an `errors` array with structured per-field detail, in addition to the existing `detail` message, matching the shape already returned by `POST /pipelines` and `PATCH /pipelines`. Existing clients that only read `detail` are unaffected. | |
| - **Richer validation errors from API v1 pipeline configuration endpoints**: A `422` response from `/pipelines/undeploy`, `/pipelines/sources/*`, `/pipelines/targets/*`, `/pipelines/processors/*`, and `/pipelines/secret-providers/*` may now include an `errors` array with structured per-field detail, in addition to the existing `detail` message. This matches the shape already returned by `POST /pipelines` and `PATCH /pipelines`. Existing clients that only read `detail` are unaffected. |
| ### Bug Fixes | ||
|
|
||
| - **Nested processor properties shown incorrectly in `redis-di describe`**: Nested objects and arrays in a processor's advanced properties are now shown as JSON instead of a raw internal format, so the `redis-di describe` output is valid and easy to read. | ||
| - **Stream could stop being processed after a Flink processor restart**: A narrow timing window around a checkpoint could leave a stream permanently unassigned to any reader after a restart (for example, following a TaskManager failure), silently halting ingestion for that stream until the pipeline was redeployed. The Flink processor now confirms with every reader before treating a stream as no longer needed. |
Contributor
There was a problem hiding this comment.
Suggested change
| - **Stream could stop being processed after a Flink processor restart**: A narrow timing window around a checkpoint could leave a stream permanently unassigned to any reader after a restart (for example, following a TaskManager failure), silently halting ingestion for that stream until the pipeline was redeployed. The Flink processor now confirms with every reader before treating a stream as no longer needed. | |
| - **Stream could stop being processed after a Flink processor restart**: A narrow timing window around a checkpoint could leave a stream permanently unassigned to any reader after a restart (for example, following a TaskManager failure). This would silently halt ingestion for that stream until the pipeline was redeployed. The Flink processor now confirms with every reader before treating a stream as deactivated. |
ZdravkoDonev-redis
force-pushed
the
RDSC-5884-rdi-1.19.1-release-notes
branch
from
August 12, 2026 05:20
c1e298a to
e9839b4
Compare
ZdravkoDonev-redis
marked this pull request as ready for review
August 12, 2026 05:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mainbut were not backported torelease.1.19.Source
The release-note content is aligned with the RDI 1.19.1 changelog in https://github.com/RedisLabs/redis-data-integration/pull/2738.
Jira: https://redislabs.atlassian.net/browse/RDSC-5884
Validation
git diff --checkNote
Low Risk
Documentation-only change: new release notes and a version string bump with no runtime or security impact.
Overview
Adds public release notes for RDI 1.19.1 and bumps
rdi_current_versionfrom1.19.0to1.19.1.The notes cover API response-body logging, a Flink processor recovery fix for streams left unassigned after restart, hardened API log redaction, and component security updates.
Reviewed by Cursor Bugbot for commit bf91043. Bugbot is set up for automated code reviews on this repo. Configure here.