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
{{ message }}
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
we are currently playing with reactive-kinesis. As first impression: It looks really good - so thanks for this cool library.
What I miss is the information about the partitionKey in each event which is available in Record.
If a shard is taken over by a different worker, we would like to drop buffered events from this shard.
Do you think it would make sense to add the key to the ConsumerEvent class?
Happy to create a PR, if you agree.
The text was updated successfully, but these errors were encountered:
Thanks @aquamatthias - apologies for the delay I got accidentally removed as a contributor so didn't receive the notifications.
This makes sense to me! I didn't think of that use case, you'd generally get notified as the worker would shutdown if I understand correctly? But additional information is all good!
@markglh Exactly. You can see one use case that I had in mind in #33 in the Akka Stream Source.
If a lease is lost I would like to throw away all buffered messages of this shard.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey,
we are currently playing with reactive-kinesis. As first impression: It looks really good - so thanks for this cool library.
What I miss is the information about the partitionKey in each event which is available in
Record
.If a shard is taken over by a different worker, we would like to drop buffered events from this shard.
Do you think it would make sense to add the key to the
ConsumerEvent
class?Happy to create a PR, if you agree.
The text was updated successfully, but these errors were encountered: