DOC-6878 Expand RDI FAQ CDC section with all supported databases - #3700
Merged
Conversation
The "How does RDI track data changes in the source database?" answer listed only Oracle, MySQL/MariaDB, PostgreSQL, and SQL Server. Expanded it to the full supported set: added MongoDB (change streams / oplog), Google Cloud Spanner (Spanner change streams, K8s/Helm only), and Snowflake (preview, Snowflake Streams), and grouped the PostgreSQL-compatible databases (Supabase, AlloyDB, Amazon Aurora/RDS for PostgreSQL, Neon) under the pgoutput bullet. Corrected the Oracle mechanism — it uses redo/archive logs via LogMiner (or XStream), not a "binary log" (that was MySQL's term). Embedded the canonical rdi-supported-source-versions.md table (and linked Prepare source databases) so the FAQ's list stays consistent with the source of truth rather than drifting. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Contributor
Contributor
🧠 Redis MemoryFound 5 related items from repository history:
Memory updated at 2b449b4 |
Remove the {{< embed-md "rdi-supported-source-versions.md" >}} table from the
CDC FAQ answer; keep the link to Prepare source databases for the complete
list and versions rather than duplicating the table into the FAQ.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
🧠 Redis MemoryFound 5 related items from repository history:
Memory updated at bf0d906 |
This was referenced Jul 29, 2026
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.
What
Resolves DOC-6878: expand the "How does RDI track data changes in the source database?" FAQ answer to cover the complete set of supported source databases, consistent with the current docs.
Changes
pgoutputbullet.LogMiner(orXStream), not a "binary log" (that was MySQL's term).rdi-supported-source-versions.mdtable (and linked Prepare source databases) so the FAQ list can't drift from the source of truth.For review
oracle.md). Flagging for a second opinion on whether to surface it in the FAQ or keep to the LogMiner default.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only edits to an FAQ; no product code, auth, or data paths.
Overview
Expands the RDI FAQ answer “How does RDI track data changes in the source database?” so it documents CDC for the full set of supported sources, not only the original four relational databases.
The section is reframed around CDC, with per-database bullets updated or added: Oracle now describes
LogMineron redo/archive logs (and optionalXStream) instead of incorrect “binary log” wording; PostgreSQL groups Supabase, AlloyDB, Aurora/RDS, and Neon underpgoutput; MongoDB, Google Cloud Spanner, and Snowflake (preview) are new, including oplog/replica-set requirements and K8s/Helm-only notes where applicable. A link to Prepare source databases points readers at the canonical supported-versions list.Reviewed by Cursor Bugbot for commit bf0d906. Bugbot is set up for automated code reviews on this repo. Configure here.