Skip to content

Explaining the caveats in writing to the same key with a workaround example#3283

Merged
andy-stark-redis merged 2 commits into
redis:mainfrom
ilianiliev-redis:writing-to-the-same-key-example
May 11, 2026
Merged

Explaining the caveats in writing to the same key with a workaround example#3283
andy-stark-redis merged 2 commits into
redis:mainfrom
ilianiliev-redis:writing-to-the-same-key-example

Conversation

@ilianiliev-redis
Copy link
Copy Markdown
Contributor

@ilianiliev-redis ilianiliev-redis commented May 7, 2026

Explaining the caveats in writing to the same key with a workaround example

Ticket: https://redislabs.atlassian.net/browse/RDSC-5181


Note

Low Risk
Low risk because this PR only updates documentation, adding guidance around delete behavior when multiple RDI jobs write to the same Redis key.

Overview
Clarifies a key caveat when multiple RDI jobs write to the same Redis key: deletes from any source entity can remove the entire target key.

Adds a new transform example, redis-write-same-key.md, showing a workaround that uses row_format: full and opcode/payload transforms to treat deletes as updates and merge nulls into Redis JSON to remove only the deleted entity’s fields while keeping the shared document intact.

Reviewed by Cursor Bugbot for commit 9d6287d. Bugbot is set up for automated code reviews on this repo. Configure here.

Copy link
Copy Markdown
Contributor

@andy-stark-redis andy-stark-redis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of suggestions, but otherwise LGTM.

Comment thread content/integrate/redis-data-integration/data-pipelines/data-denormalization.md Outdated
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
@andy-stark-redis andy-stark-redis merged commit 817fe46 into redis:main May 11, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants