-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose redeliverUnacknowledgedMessages(Set<MessageIdImpl> messageIds) in the public API #2211
Comments
@jnioche Yes, I still agree we should expose this in public API, perhaps with a slightly different signature: redeliverMessages(Collection<MessageId> messageIds) |
thanks @merlimat. What about being able to set a delay? Is that possible? |
@jnioche could you summarize the slack conversation in the description here? |
@ConcurrencyPractitioner I think this is in a way superceded by the negative acks feature in master. At this point I’d wait to see if there is still a gap to be filled, before adding one more API |
currently negative acks feature is done, this is not blocked anymore. Anyone would like to contribute to this please feel free to comments on this issue. |
I think the feature requested for able to ask message(s) to be redelivered with certain delay is supported by this pr: #6449. |
Haven't checked the PR mentioned above but it looks like it does provide this functionality indeed. Thanks everyone |
See discussion on slack
Ideally, I'd love to be able set a delay for when the message(s) will be consumable again. I gather this is not currently possible, but would it be feasible at all or is there something in the architecture that would prevent adding such a feature?
The text was updated successfully, but these errors were encountered: