[
https://issues.apache.org/jira/browse/KAFKA-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115063#comment-16115063
]
Randall Hauch commented on KAFKA-5704:
--------------------------------------
As of Kafka 0.11.0.0, the Kafka Connect distributed worker will automatically
create the internal topics (see KAFKA-4667) using the new KafkaAdminClient.
However, the KafkaAdminClient will throw an UnsupportedVersionException if the
broker version doesn't support the necessary API (which in this case is the
[{{CREATE_TOPICS}}
API|https://github.com/apache/kafka/blob/0.10.1/clients/src/main/java/org/apache/kafka/common/protocol/ApiKeys.java#L42]
added in 0.10.1.0). That means contrary to the [notes in
KAFKA-4667|https://issues.apache.org/jira/browse/KAFKA-4667?focusedCommentId=15998675&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15998675],
Kafka Connect can indeed work with brokers older than 0.10.1.0, will receive
the exception in such a case, and will not properly handle the exception.
> Auto topic creation causes failure with older clusters
> ------------------------------------------------------
>
> Key: KAFKA-5704
> URL: https://issues.apache.org/jira/browse/KAFKA-5704
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.11.0.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Randall Hauch
>
> The new automatic internal topic creation always tries to check the topic and
> create it if missing. However, older brokers that we should still be
> compatible with don't support some requests that are used. This results in an
> UnsupportedVersionException which some of the TopicAdmin code notes that it
> can throw but then isn't caught in the initializers, causing the entire
> process to fail.
> We should probably just catch it, log a message, and allow things to proceed
> hoping that the user has already created the topics correctly (as we used to
> do).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
