[
https://issues.apache.org/jira/browse/KAFKA-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921298#comment-17921298
]
Ismael Juma commented on KAFKA-18648:
-------------------------------------
[~chia7712] While that is true, it's still widely used (along with its fork).
I'm working with Emanuele Sabellico to figure out if this is the only issue
affecting kafka-python or if there are others. Depending on the outcome, I'll
post my recommendation here.
> kafka-python requires metadata request version 1
> ------------------------------------------------
>
> Key: KAFKA-18648
> URL: https://issues.apache.org/jira/browse/KAFKA-18648
> Project: Kafka
> Issue Type: Bug
> Reporter: Ismael Juma
> Assignee: Ismael Juma
> Priority: Blocker
> Fix For: 4.0.0
>
>
> KIP-896 captured protocol api support from a few clients including
> kafka-python. However, when we actually test a client, unexpected
> dependencies can sometimes be uncovered.
> It turns out that kafka-python has a path where the metadata version used is
> hardcoded to be v0 or v1:
> [https://github.com/dpkp/kafka-python/blob/a6d0579d3cadd3826dd364b01bc12a2173139abc/kafka/client_async.py#L835]
> We need to decide whether we keep the existing behavior in 4.0/trunk and
> update the KIP to reflect that kafka-python won't work without a (small)
> change or add back support for Metadata request v1-v3.
> I also filed an issue with kafka-python-ng (which is a fork of the original
> that is not abandoned).
> https://github.com/wbarnha/kafka-python-ng/issues/208
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
