THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Discussion thread: here
JIRA: here
The proposal discussed in this KIP is implemented in this pull request.
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
...
Config Option | Description | Default Value | Domain |
---|---|---|---|
errors.log.enable | Log the error context (the base information, configs of various stages and the record which caused the failure) along with the other application logs. | false | Boolean |
errors.log.include.configs | Include the (connector) whether to include the configs in the log. | false | Boolean |
errors.log.include.messages | Include whether to include the Connect Record which failed to process in the log. | false | Boolean |
...
Config Option | Description | Default Value | Domain |
---|---|---|---|
errors.deadletterqueue.enable | Write the error context (the base information, configs of various stages and the record which caused the failure) into a Kafka topic | false | Boolean |
errors.deadletterqueue.topic.name | The name of the topic where these messages are written to | "" | A valid Kafka topic name |
errors.deadletterqueue.topic.partitions | Number of partitions for this topic | 5 | [1, 2 .. Integer.MAX_INT] |
errors.deadletterqueue.topic.replication.factor | The replication factor for this topic | 3 | [1, 2 .. Short.MAX_SHORT] |
errors.deadletterqueue.include.configs | Include the (connector) whether to include the configs in the log. | false | Boolean |
errors.deadletterqueue.include.messages | Include the Connect Record which whether to include the record which failed to process in the log. | false | Boolean |
errors.deadletterqueue.producer.* | Config for the KafkaProduce to produce to this topic (for example: errors.dlq.producer.bootstrap.servers will set the bootstrap servers of the Kafka cluster). |
...