Changelog
Make MySQL and CockroachDB change streaming more resilient
Recover MySQL CDC safely and keep CockroachDB streams accurate through routine changes.
MySQL pipelines could fail to resume after GTID mode changes or anonymous transactions, while ordinary CockroachDB changes such as empty deletes, new columns, and wide decimals could stop a stream or lose numeric precision.
Artie now chooses MySQL GTID resume only when the saved position is safe, falls back to file-and-position recovery when needed, and keeps offsets usable as GTID mode changes. CockroachDB streaming now skips deletes that removed no row, recognizes newly added columns in earlier queued changes, and preserves exact decimal text rather than converting it through a floating-point value.
This is for teams running MySQL or CockroachDB CDC pipelines that need reliable recovery and accurate replicated values through routine database changes.
Why this matters
- Resume MySQL CDC safely through GTID mode transitions
- Keep CockroachDB streams running through no-op deletes and schema additions
- Preserve precision for wide and unbounded CockroachDB decimals