This release adds a new config option dlq.send.batch.on.error that gives you better control over Dead Letter Queue behavior when parsing errors hit. Turn it on, and the connector sends the whole batch straight to the DLQ instead of trying each record one-by-one against the database. This prevents the connector from falling behind and building up message lag, especially useful on high-latency networks where those individual retries can really slow things down. We've set it to false by default, so you keep the existing behavior where the connector tries to save as many good records as possible.
What's Changed
Full Changelog: v0.16...v0.17
Contributors
jerrinot