Dominic Evans
Dominic Evans
It’s a tricky one because it’s not something we can easily do in a v1 release. We’d have to jump to /v2 to make the breaking change and we’ve had...
@juwell are you still seeing this problem today or did you resolve it? It certainly does seem like your client was exceeding the read timeout (`c.Net.ReadTimeout = 30 * time.Second`)...
As noted that even our own internals fail due the errcheck linter on offsetManager.Commit, it probably makes sense to defer this to `v2`
> [Sarama] 2025/10/24 16:19:22 client/metadata got error from broker -1 while fetching metadata: kafka server: The version of API is not supported Have you set Version in sarama.Config correctly to...
Sure, but as announced in [1.41.0 release notes](https://github.com/IBM/sarama/releases/tag/v1.41.0) under “breaking changes” we purposefully bumped the _default_ version to give a better out of the box experience for most Sarama users...
> OK, but the fact is that setting `conf.Version = sarama.V0_10_2_2` for Kafka 0.10.x.x isn't working properly. Is there any way to fix this? Or should I abandon it? 😂...
Correct yes, it would only effect people importing and calling into `kafka_sarama` itself. I agree that a breaking change release note is probably sufficient. Ultimately there won't be any more...
@Tangxinqi if you're able to do some testing after running `go get github.com/IBM/sarama@main && go mod tidy` to confirm that it resolves these issues for you that'd be very welcome!
Dupe of #3166