errors.deadletterqueue.topic.name 是否适用于源连接器
Does errors.deadletterqueue.topic.name work for source connector
"errors.deadletterqueue.topic.name" 是否适用于源连接器？我用 JDBC sink connector 进行了测试，它可以工作，但是我没有发现有序列化错误的记录进入死信队列。
我用的Debezium Connector for MongoDB and apache-kafka-connect版本是2.4.0。
其余错误处理配置：
"errors.tolerance": "all",
"errors.log.enable": "false",
"errors.deadletterqueue.topic.name": "test-dlq",
"errors.deadletterqueue.context.headers.enable": "true"
apache-kafka-connect has included error handling options, including the functionality to route messages to a dead letter queue since Apache Kafka 2.0 through KIP-298: Error Handling in Connect. According this KIP, Dead Letter Queue is supported 仅适用于接收器连接器。
您也可以查看 Kafka Connect docs：
errors.deadletterqueue.topic.name: The name of the topic to be used as the dead letter queue (DLQ) for messages that result in an error when processed by this sink connector, or its transformations or converters. The topic name is blank by default, which means that no messages are to be recorded in the DLQ.
的精彩文章
"errors.deadletterqueue.topic.name" 是否适用于源连接器？我用 JDBC sink connector 进行了测试，它可以工作，但是我没有发现有序列化错误的记录进入死信队列。
我用的Debezium Connector for MongoDB and apache-kafka-connect版本是2.4.0。
其余错误处理配置：
"errors.tolerance": "all",
"errors.log.enable": "false",
"errors.deadletterqueue.topic.name": "test-dlq",
"errors.deadletterqueue.context.headers.enable": "true"
apache-kafka-connect has included error handling options, including the functionality to route messages to a dead letter queue since Apache Kafka 2.0 through KIP-298: Error Handling in Connect. According this KIP, Dead Letter Queue is supported 仅适用于接收器连接器。
您也可以查看 Kafka Connect docs：
errors.deadletterqueue.topic.name: The name of the topic to be used as the dead letter queue (DLQ) for messages that result in an error when processed by this sink connector, or its transformations or converters. The topic name is blank by default, which means that no messages are to be recorded in the DLQ.
的精彩文章