Pulsar: Expose redeliverUnacknowledgedMessages(Set<MessageIdImpl> messageIds) in the public API

Created on 20 Jul 2018  路  8Comments  路  Source: apache/pulsar

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?

help wanted triagweek-43 typenhancement typfeature

All 8 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?

@jnioche @sijie If you are alright with it, I could pick up this one.

@ConcurrencyPractitioner I think this is in a way superceded by the negative acks feature in master. At this point I鈥檇 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: https://github.com/apache/pulsar/pull/6449.
Can just close this one.

Haven't checked the PR mentioned above but it looks like it does provide this functionality indeed. Thanks everyone

Was this page helpful?
0 / 5 - 0 ratings