Configure Debezium signaling table for ad-hoc incremental snapshots
domain: debezium.io · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a signaling table in the source database with columns id (VARCHAR), type (VARCHAR), and data (VARCHAR or TEXT)
Set the signal.data.collection connector property to the fully qualified name of the signaling table
Grant the Debezium database user INSERT privileges on the signaling table
To trigger an incremental snapshot, INSERT a row with type set to execute-snapshot and data containing a JSON payload specifying data-collections (the tables to snapshot)
Monitor the Debezium connector log or metrics to confirm the incremental snapshot is in progress and completes
Incremental snapshots use a watermark-based algorithm so they can run concurrently with streaming CDC without stopping the connector
Known gotchas
The signaling table must be included in the connector's table.include.list (or not excluded) so Debezium captures changes from it; otherwise signals are not processed
Incremental snapshots do not guarantee strict ordering with streaming events for the same record during the snapshot window; deduplicate by source offset when necessary
The signal.data.collection property name and exact column schema requirements may vary slightly by connector type (MySQL, PostgreSQL, etc.); consult the connector-specific docs
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?