[
https://issues.apache.org/jira/browse/KAFKA-12995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369479#comment-17369479
]
Alan Artigao Carreño commented on KAFKA-12995:
----------------------------------------------
I've created a PR [#10929|https://github.com/apache/kafka/pull/10929] but I
can't assign to me the ticket.
> AdminClient listOffsets fail with old Kafka Broker
> --------------------------------------------------
>
> Key: KAFKA-12995
> URL: https://issues.apache.org/jira/browse/KAFKA-12995
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Reporter: Alan Artigao Carreño
> Priority: Major
>
> The implementation of KAFKA-5291 introduced a check for old Brokers
> compatibility falling back to _*true*_ in *MetadataRequest
> allowAutoTopicCreation* field for some operations like *describeTopics*.
> Then, after that backward-compatibility changes, more methods were added to
> *AdminClient* like *listOffsets*
> [KIP-396|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=97551484]
> which unfortunately don't have compatibility with old Brokers into account.
> One might argue that, given that new methods were not present previously,
> it's not a compatibility break. While this is strictly true, I believe that
> one of Kafka Clients' most appreciated feature is the ability to use old
> Brokers with new Clients.
> I've prepared a small PR to fix for this, following the same approach used in
> KAFKA-5291.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
