You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that i think about it, I remembered what you told me when i was first discovering the lib
It takes a slightly different approach: rather than implementing the wire protocol, it wraps the Java client.
So i wonder if actually Kafka4s needs to do anything specific here. In my understanding it would just work. Indeed, I try to find any reference to assignement strategy in code, and there is nothing about it.
Now, i am not versed enough in the current code base to know if there is an interplay between the rebalance protocol and and the current code base and in particular with the usage of stream. For instance, (1) are things implemented to handle the eager rebalance protocol only, which will include a range of assignor (roundrobin, range, sticky, ....) but not the cooperative one, as partition can be revoked individually. (2) Or maybe all of this in delegated to the underlying client and is transparent to the higher level api.
I know that in the case of fs2-kafka they have had to do something specific for the cooperativeSticky assignor, and even then the support is currently not without bug apparently.
Hope it make sense and give enough context to my question.
Hi, just wondering if kafka4s handle the new CooperativeStickyAssignor well ?
The text was updated successfully, but these errors were encountered: