Change Data Capture Pipeline · View 15 of 21 · Runtime
Decisions
- Compatible changes propagate without a human; breaking ones pause one table and raise a decision (ADR-08).
- A primary-key change is a re-snapshot, not a migration: the sink's keys no longer mean what they meant.
- There is no third outcome for an unregistered column — propagate it or exclude it by allow-list. Silently dropping it is the failure this row exists to forbid.
Numbers
- Compatible change propagates within 60 s; breaking change pauses within 10 s (assumptions).
- A pause holds the table's position; the platform refuses a pause that would outlive source log retention.
Risks
- Classification is the single point of judgement in the pipeline: a widened type misread as narrowed pauses needlessly, and the reverse corrupts a sink.
- Detection depends on the source emitting decodable relation metadata; a source that does not is a polling fallback and loses this whole view.