You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2018/06/05 21:00:00 UTC
[jira] [Resolved] (KAFKA-6981) Missing Connector Config
(errors.deadletterqueue.topic.name) kills Connect Clusters
[ https://issues.apache.org/jira/browse/KAFKA-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ewen Cheslack-Postava resolved KAFKA-6981.
------------------------------------------
Resolution: Fixed
Issue resolved by pull request 5125
[https://github.com/apache/kafka/pull/5125]
> Missing Connector Config (errors.deadletterqueue.topic.name) kills Connect Clusters
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-6981
> URL: https://issues.apache.org/jira/browse/KAFKA-6981
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Arjun Satish
> Assignee: Arjun Satish
> Priority: Major
> Fix For: 2.0.0
>
>
> The trunk version of AK currently tries to incorrectly read the property (errors.deadletterqueue.topic.name) when starting a sink connector. This fails no matter what the contents of the connector config are. The ConnectorConfig does not define this property, and any calls to getString will throw a ConfigException (since only known properties are retained by AbstractConfig).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)