Repository navigation
DOC-7143: Add a scripted Redis Data Integration interactive demo - #4177
Merged
Merged
Conversation
A browser-only demo for the Iris launch, in the same style and with the same food delivery sample data as the other Iris demos, here as PostgreSQL tables. Readers deploy a pipeline as hashes or JSON and watch the initial sync write default keys; run inserts, updates, and a delete and follow each change through PostgreSQL, the collector, and the stream processor into Redis; and deploy a job file for customers, with an annotated key expression and remove_field step, then see that a job only affects new changes, that a reset leaves the old keys, and that only a flush cleans up. Key patterns, opcodes, type mapping, config.yaml and job syntax, the redis-di status layout, and the reset and flush behavior follow the RDI docs. The data and timings are illustrative. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
|
Contributor
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at fdca4a5 |
EliShteinman
added a commit
to EliShteinman/docs
that referenced
this pull request
Oct 5, 2026
Adds a scripted in-browser RDI interactive demo page and its rdi-demo shortcode, CSS, and JS. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
A browser-only demo for the Iris launch, in the same style and with the same food delivery sample data as the other Iris demos, here as PostgreSQL tables. Readers deploy a pipeline as hashes or JSON and watch the initial sync write default keys; run inserts, updates, and a delete and follow each change through PostgreSQL, the collector, and the stream processor into Redis; and deploy a job file for customers, with an annotated key expression and remove_field step, then see that a job only affects new changes, that a reset leaves the old keys, and that only a flush cleans up.
Key patterns, opcodes, type mapping, config.yaml and job syntax, the redis-di status layout, and the reset and flush behavior follow the RDI docs. The data and timings are illustrative.
Note
Low Risk
Documentation and static front-end only; no production services, auth, or data paths are touched.
Overview
Adds a browser-only Redis Data Integration (RDI) interactive demo for the Iris docs: a new page under Data Integration, a Hugo
rdi-demoshortcode, and client-side assets (rdi-demo.js/rdi-demo.css) that reuse the Context Retriever demo look and food-delivery sample data.Readers walk through three tabs—initial sync (hash vs JSON, deploy, snapshot to default keys), CDC (pick SQL inserts/updates/deletes and trace PostgreSQL → collector → stream processor → Redis), and job files (annotated
customersjob withremove_fieldandcustomer:{id}keys, then update / reset / flush to show jobs only affecting new changes and leftover keys). Config, job YAML, opcodes, andredis-di statusoutput are modeled to match RDI docs; nothing calls a real pipeline.The Data Integration index Quick example section now links to this demo as a no-setup alternative to the quick start.
Reviewed by Cursor Bugbot for commit fdca4a5. Bugbot is set up for automated code reviews on this repo. Configure here.