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
When sending Subscribe.AutoPartitionWithManualOffset to the KafkaConsumerActor, the assignedListener and revokedListener functions may end up capturing the actor instance. The current API also makes it difficult to use non-blocking code to load the offsets.
For safe use in actors, it would be useful to have a wrapper around assignedListener and revokedListener that works by asking a supplied ActorRef for a response (Offsets) to AssignedListeners(topics: List[TopicPartition) and RevokedListeners(...).
The text was updated successfully, but these errors were encountered:
Yeah, that would be nice indeed. The problem is that the underlying Java client doesn't support asynchronous listeners. The Java client revocation/assignment hooks must complete their work during the call.
When sending
Subscribe.AutoPartitionWithManualOffset
to theKafkaConsumerActor
, theassignedListener
andrevokedListener
functions may end up capturing the actor instance. The current API also makes it difficult to use non-blocking code to load the offsets.It would be more convenient to have
For safe use in actors, it would be useful to have a wrapper around
assignedListener
andrevokedListener
that works by asking a suppliedActorRef
for a response (Offsets
) toAssignedListeners(topics: List[TopicPartition)
andRevokedListeners(...)
.The text was updated successfully, but these errors were encountered: