Per-Table Pause Control
Pause replication for a single table while the rest of the pipeline keeps streaming, with changes held in Kafka and reminders sent after two days.
Sometimes you need to make a change to a single table - a migration, a cleanup, a schema tweak - without touching the rest of your pipeline. Previously, pausing replication meant pausing the entire stream, which worked but wasn’t ideal for teams juggling table-level maintenance on busy systems. This update gives you more precise control without disrupting healthy tables.
You can now pause replication for an individual table while the rest of the pipeline keeps streaming as usual. If you need to work on a table like orders, you can temporarily pause it, perform your updates, and resume when ready - with zero impact to other tables. Artie continues capturing changes for the paused table in Kafka, ensuring nothing is lost, and automated reminders kick in after two days so paused tables never slip through the cracks.
Why this matters:
- Gives fine-grained control during table-level maintenance or troubleshooting
- Avoids unnecessary downtime by keeping the rest of the pipeline running
- Captures all changes for the paused table so no updates are missed
- Sends reminders after two days to prevent data loss from Kafka’s 14-day retention window
- Helps maintain CDC continuity even during complex schema work