How to handle when api version response isn't helpful

[jeremysgh]

I have a consumer using librdkafka 2.5.0 via confluent-kafka-go. The broker, controlled by another party, is 3.2.x and using inter.broker.protocol.version=2.7 and log.message.format.version=2.7. The api version request completes and the consumer later attempts to use FetchRequest v13 but fails with UNKNOWN_TOPIC_ID. Metadata does not include a topic id. Apparently FetchRequest v13 with topic id was introduced in 2.8 (KIP-516).

I tried api.version.request=false with broker.version.fallback=2.7, but rd_kafka_new() ignores because the fallback version should support the api version request. I also tried broker.version.fallback=0.9.0.1, but I'm getting truncated messages.

Other than convincing the broker operator to change, are there any workarounds? Is librdkafka from before broker 2.8 my only other option?