Hello!
Apache Kafka 4.0 is introducing KIP-896, a KIP which deprecates client protocol API versions. For the exact list of deprecated versions, please refer to the KIP: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235838251#KIP896:RemoveoldclientprotocolAPIversionsinKafka4.0-PublicInterfaces
Since this library uses aiokafka according to the readme, I wanted to raise attention to an issue that was found in aiokafka's support of the metadata request key as suggested in this issue: aio-libs/aiokafka#1085.
If indeed there is a problem, that would mean Faust would not work with AK 4.0 brokers. It seems otherwise Faust is configured to support the latest API version common across both client and broker https://faust-streaming.github.io/faust/userguide/settings.html#broker-api-version
Hello!
Apache Kafka 4.0 is introducing KIP-896, a KIP which deprecates client protocol API versions. For the exact list of deprecated versions, please refer to the KIP: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235838251#KIP896:RemoveoldclientprotocolAPIversionsinKafka4.0-PublicInterfaces
Since this library uses aiokafka according to the readme, I wanted to raise attention to an issue that was found in aiokafka's support of the metadata request key as suggested in this issue: aio-libs/aiokafka#1085.
If indeed there is a problem, that would mean Faust would not work with AK 4.0 brokers. It seems otherwise Faust is configured to support the latest API version common across both client and broker https://faust-streaming.github.io/faust/userguide/settings.html#broker-api-version