[
https://issues.apache.org/jira/browse/ARTEMIS-4553?focusedWorklogId=898502&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-898502
]
ASF GitHub Bot logged work on ARTEMIS-4553:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Jan/24 17:45
Start Date: 08/Jan/24 17:45
Worklog Time Spent: 10m
Work Description: jbertram commented on PR #4730:
URL:
https://github.com/apache/activemq-artemis/pull/4730#issuecomment-1881552171
> Good catch, I hadn't thought to this use case but if that would be
supported then `a*c` would be more specific of `a*`
What about multiple `*` characters? For example, would `a*c*` match `abcd`
and `ac` and `abc`?
> This is an important point from the development point of view, are you
thinking to any specific cases?
I'm not thinking about any specific case. I'm mainly thinking that the
possible combinations that need to be tested will increase substantially with
this change, especially if multiple `*` characters are supported.
This change will mean that while `*` by itself still means **a single word**
when `*` is combined with other characters it will completely change its
meaning to **zero or more characters**. I think this will ultimately hurt
usability.
Issue Time Tracking
-------------------
Worklog Id: (was: 898502)
Time Spent: 1h (was: 50m)
> Support partial word matches for address settings
> -------------------------------------------------
>
> Key: ARTEMIS-4553
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4553
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Domenico Francesco Bruscino
> Assignee: Domenico Francesco Bruscino
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently, though the documentation specifies that the "*" wildcard matcher
> is only intended to match a complete word (delimited string using the
> configured delimiter), it appears that it also works for partial word
> matches, like "
> Could this behavior be supported and documented going forward, as reverting
> this behavior would break existing configurations?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
