[
https://issues.apache.org/jira/browse/KAFKA-9046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974034#comment-16974034
]
ASF GitHub Bot commented on KAFKA-9046:
---------------------------------------
omkreddy commented on pull request #7525: KAFKA-9046: Use top-level worker
configs for connector admin clients
URL: https://github.com/apache/kafka/pull/7525
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Connect worker configs require undocumented 'admin.' prefix to configure DLQ
> for connectors
> -------------------------------------------------------------------------------------------
>
> Key: KAFKA-9046
> URL: https://issues.apache.org/jira/browse/KAFKA-9046
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.3.0, 2.4.0, 2.3.1
> Reporter: Chris Egerton
> Assignee: Chris Egerton
> Priority: Blocker
>
> The changes for KAFKA-8265 involved [adding a prefix of "admin." to Connect
> worker
> configs|https://github.com/apache/kafka/pull/6624/files#diff-316d2c222b623ee65e8065863bf4b9ceR606]
> that would be used to configure the admin client that's used for connector
> DLQs. However, this was never documented in the [corresponding
> KIP|https://cwiki.apache.org/confluence/display/KAFKA/KIP-458%3A+Connector+Client+Config+Override+Policy]
> and has broken backwards compatibility with prior Connect releases since
> workers without the necessary {{"admin."}}-prefixed properties in their
> configuration files will now fail in some circumstances (e.g., when
> interacting with a secured Kafka cluster that requires authentication from
> all admin clients that interact with it).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
