[
https://issues.apache.org/jira/browse/ARTEMIS-4510?focusedWorklogId=910064&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910064
]
ASF GitHub Bot logged work on ARTEMIS-4510:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Mar/24 08:37
Start Date: 15/Mar/24 08:37
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4681:
URL:
https://github.com/apache/activemq-artemis/pull/4681#issuecomment-1999173285
@clebertsuconic
The use-case for me (and another user I spoke to on the slack channel) is to
be able to compute a destination during runtime inside the transformer. The
other user was after something like "If message has header X, address =
somePrefix + headerX"
I want to use this for a global routing system that would look something
like this:
1. Divert wildcard-matches destinations following a naming system that
includes a site name (this matches a few hundred destinations, destinations are
created dynamically by clients).
2. Divert adds some metadata to messages and aggregates them to a
common/aggregate destination (no auto-create needed here)
3. A core bridge picks these messages up and sends them to their destination
site.
4. A Divert on the destination site routes messages from the aggregate
destination and back to their original destination name (or in some cases
another related destination name), based on logic in a transformer (ultimately
changing the messages address)
I do not want to use the __AMQ_ORIGINAL_DESTINATION headers for this as in
the event of some network issues or similar messages would end up on a DLA
whereby said header changes to the aggregate queue name and identification
afterwards becomes... labour intensive...
Issue Time Tracking
-------------------
Worklog Id: (was: 910064)
Time Spent: 3h 10m (was: 3h)
> Add auto-create-destination logic to diverts
> --------------------------------------------
>
> Key: ARTEMIS-4510
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4510
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> This enables the use of dynamic routing decisions within the transformer by
> setting the message address. It also covers for a rare problem where if any
> of the forwarding addresses are removed during runtime, such as from
> auto-delete, the message would get silently dropped.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
