[ 
https://issues.apache.org/jira/browse/ARTEMIS-4510?focusedWorklogId=910122&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-910122
 ]

ASF GitHub Bot logged work on ARTEMIS-4510:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Mar/24 14:42
            Start Date: 15/Mar/24 14:42
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on PR #4681:
URL: 
https://github.com/apache/activemq-artemis/pull/4681#issuecomment-1999817123

   @AntonRoskvist being 100% open about this... I have a disagreement point 
with @jbertram on this. I think if you Divert to an address foo, that address 
should be part of the verification of the auto-create. Justin thinks that's a 
breaking change, and I see it as a bug.... 
   
   Maybe you could open a discuss thread on the dev-list to talk about it and 
find consensus among other people?
   
   IMO we should just document the change and tell users if they must route to 
nowhere they should have either a disabled auto-create on the 
Address-settings.. or an empty MultiCast address (eg address ReturnedItems or 
Orders without a subscription).
   
   
   
   One thing I 100% agree with Justin though is that we shouldn't penalize the 
regular case with checking auto-create every time. We need to find an optimal 
way of doing it.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 910122)
    Time Spent: 3.5h  (was: 3h 20m)

> 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: 3.5h
>  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)

Reply via email to