Denis Otkidach

@aisven Sorry for long delay. `aiokafka` already used `cramjam` for other codecs and `cramjam` provides LZ4, so it's a way to remove one more dependency. If I understand correctly, the...

Hi @Tinanuaa, thank you for reporting the issue. It's unclear from the report, have you tried version 0.11.0? The symptom looks pretty much like #983, [fixed](https://github.com/aio-libs/aiokafka/pull/1007) in the latest release.

No, consumer instance is not reusable, you have to recreate it.

It's possible to fix this, but I wouldn't expect somebody to invest their time in it.

> Are there any plans regarding adding support for the 4.0 version. Any update would be great I’m not planning to implement it myself. But if someone volunteers to do...

`aiokafka` allows to supply custom serializer/deserialer [as well](https://aiokafka.readthedocs.io/en/latest/examples/serialize_and_compress.html). But this feature is considered for deprecation, since it stands in the way of adding type annotations.

> The type annotations could be resolved with a type parameter on the consumer/producer class. This makes consumer and producer _classes_ generic of 2 parameters, the types accepted by serializer/returned...

Right now, when passing consumer (and similar for producer) around, you can declare it as `AIOKafkaConsumer`. But when types are added and we make it generic, it will be turned...

> I guess then "wrapper" classes could be a solution ? Right, it's one of the possible solution. Another one could be to make generic methods that accept (de)serializers instead...

> [#496](https://github.com/aio-libs/aiokafka/discussions/949) I wrote about this issues. @ods can you review it? thx Sorry, my competence is not enough to propose a correct fix to the problem. The suggested change...