Peter Dannemann

I don't think this is a change we can accommodate due to how much it could disrupt users of this library. If you application is doing frequent small writes why...

I agree with the sentiment, I think making things more configurable to support lower level use cases like this is really the only option as you mentioned. It will come...

@zachxu42 this seems like a plausible fix but given that we've broken kafka-go before trying to fix this issue I would feel a lot better if we first found some...

We spent some more time comparing this to https://github.com/segmentio/kafka-go/pull/1177 and we think that is more of a root cause fix, but I think we'll still need to make some testing...

The Reader buffers messages under the hood and you can configure the size of this queue with `ReaderConfig.QueueCapacity` as well as the size of the fetch request via `ReaderConfig.MaxBytes`, it...

I think this is likely due to the same underlying issue as https://github.com/segmentio/kafka-go/issues/1093, which is exactly what you mentioned at the bottom of your issue about us needing to support...

This comment here maybe provides some more insight https://github.com/twmb/franz-go/issues/249#issuecomment-1357853449

@aratz-lasa this seems like a plausible fix but given that we've broken kafka-go before trying to fix this issue I would feel a lot better if we first found some...

@wangrenyi should we mark this as resolved then? The fix was to add the version to the request?

Ok so it sounds like you are using a different API version for kafka-go and confluent-kafka-go and as they are using the same consumer group this is creating issues. I...