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

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

                Author: ASF GitHub Bot
            Created on: 06/Jul/23 15:48
            Start Date: 06/Jul/23 15:48
    Worklog Time Spent: 10m 
      Work Description: gemmellr commented on PR #4541:
URL: 
https://github.com/apache/activemq-artemis/pull/4541#issuecomment-1623910314

   I wouldn't change it in this way either. It is a breaking change as Justin 
says, very questionable for whats only marked as a 'minor improvement', and as 
the ClientID and address are ultimately distinct things and the wildcard 
deliminator is about the address its also not clear to me either that this 
would really be 'more consistent'.




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

    Worklog Id:     (was: 869608)
    Time Spent: 1h  (was: 50m)

> MQTT queue creation does not honor the delimiter and always uses '.'
> --------------------------------------------------------------------
>
>                 Key: ARTEMIS-4350
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4350
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: MQTT
>    Affects Versions: 2.29.0
>            Reporter: Erwin Dondorp
>            Priority: Minor
>         Attachments: 1.png, 2.png
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> When subscribing using an MQTT client on an address, a subscription queue is 
> created.
> For MQTT, the subscription-queue has a name that is constructed using the 
> client-id and the address-name. The parts are always joined using the {{.}} 
> character.
> It is more consistent when the _delimiter_ character is used for that.
> a PR will be added
> using {{/}} as separator, before:
> !1.png!
> using {{/}} as separator, after:
> !2.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to