[ 
https://issues.apache.org/jira/browse/KAFKA-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498841#comment-16498841
 ] 

ASF GitHub Bot commented on KAFKA-6981:
---------------------------------------

wicknicks opened a new pull request #5125:  KAFKA-6981: Move the error handling 
configuration properties into the ConnectorConfig and SinkConnectorConfig 
classes
URL: https://github.com/apache/kafka/pull/5125
 
 
   *More detailed description of your change,
   if necessary. The PR title and PR message become
   the squashed commit message, so use a separate
   comment to ping reviewers.*
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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)

Reply via email to