You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2023/03/29 07:34:00 UTC
[jira] [Resolved] (CAMEL-19210) camel-pulsar - Support for delayed delivery pulsar messages using deliverAt
[ https://issues.apache.org/jira/browse/CAMEL-19210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-19210.
---------------------------------
Resolution: Fixed
> camel-pulsar - Support for delayed delivery pulsar messages using deliverAt
> ---------------------------------------------------------------------------
>
> Key: CAMEL-19210
> URL: https://issues.apache.org/jira/browse/CAMEL-19210
> Project: Camel
> Issue Type: Improvement
> Components: camel-pulsar
> Reporter: Alastair Burr
> Priority: Minor
> Fix For: 3.21.0, 4.0-M3, 4.0
>
>
> *Description*
> Support for delayed delivery pulsar messages using deliverAt
> *Proposed change*
> To add in the ability to set the delayed delivery of Pulsar messages by use of a header. This would use the deliverAt() functionality on the Pulsar producer which simply takes in the a timestamp in milliseconds based on UTC
> https://pulsar.apache.org/api/client/2.11.x/org/apache/pulsar/client/api/TypedMessageBuilder.html#deliverAt(long)
> *Background:*
> Delayed delivery is a very useful feature within Pulsar that can be used for a number of scenarios where you want the message to be picked up at a particular time.
> There is additionally a deliverAfter() method on the Pulsar producer where you can specify a time period instead of a specific time, but the implementation behind the scenes just turns this into a timestamp then uses that. As such just implementing deliverAt() provides enough flexibility to the clients.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)