Loïc Mathieu

@FroMage yes, it's OK for me, I follow the discussion and had nothing to say ;)

> Taking into accound the lag of all topics of the configured consumer group Just seen this one is handled here : https://github.com/kedacore/keda/pull/2409, great ;) But I still think it...

@tomkerkhove some typical Kafka deployment involves multiple topic, for eg one topic by country. So you usually use a regex. And configuring hundreds of scaler is not very practical. Moreover,...

I agree that a list of topic can be replaced by multiple scalers but not the usage of a regex (moreover, regex target topics can be un-known at build time).

@zroubalik well I would love to but I'm pretty new to Go and the Sarama client didn't allow pattern based consumption OOTB so it may not be a trivial implementation....

Another solution to using a `@Transactional` annotation would be to create another acknowledgement mode: `@Acknowledgment(TRANSACTED)` or to provides a `@IncominOutgoing(incomming="in", outgoing="out", transactional=true)` annotations.

Yes, I have a working prototype for Quarkus here: https://github.com/quarkiverse/quarkiverse-google-cloud-services/pull/55 But it's not merged as the corresponding component on smallrye seems to not be actively maintained, if it changed, I'll...

@carlesarnal I just use the schema registry docker container with only confluent serializer/deserializer and the error pops up from time to time inside my test cases (which use testcontainers to...

@carlesarnal I have no idea there was such settings and also have no idea how to increase it via the docker image.

Thanks @carlesarnal I'll try it tomorrow and let you know