CAMEL-19210 - Support for delayed delivery pulsar messages using deliverAt (for main) #9660
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Duplicate of #9659 for main!
Description
This functionality allows for delayed delivery options within Apache Pulsar to be used by specifying a time that you want the message to be delivered.
This is simply is a passthrough for setting the deliverAt() on an Apache Pulsar message used used by the producer. The expected value is a Long representing the current timestamp in milliseconds (UTC) which is simply passed across without translation.
The detail of the call used is as follows:
https://pulsar.apache.org/api/client/2.11.x/org/apache/pulsar/client/api/TypedMessageBuilder.html#deliverAt(long)
Uses the CamelPulsarProducerMessageDeliverAt header name for setting.
Target
camel-3.x, whereas Camel 4 uses themainbranch)Tracking
Apache Camel coding standards and style
I checked that each commit in the pull request has a meaningful subject line and body.
I formatted the code using
mvn -Pformat,fastinstall install && mvn -Psourcecheck