Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 431512 - Include # and * wildcard information
Include # and * wildcard information
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Programming_Reference (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jonathan Robie
Kim van der Riet
Depends On:
  Show dependency treegraph
Reported: 2008-02-05 01:42 EST by Lana Brindley
Modified: 2013-10-23 19:06 EDT (History)
3 users (show)

See Also:
Fixed In Version: B4
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-19 09:32:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Lana Brindley 2008-02-05 01:42:49 EST
Description of problem:

Questions from beta customer:

> 3. How does a wildcard work with the routing key? The documents you mentioned
only talk about the "#" character. Does "a.#" match "a.b" and "a.b.c"? In some
document (which I didn't note down), there was talk of "*" matching one word and
"#" matching zero or more words. Is this true? Is there a list of wildcard
examples some place?
“*” matches a single word and ‘#’ matches zero or more words.

This information should be included in the Tutorial for GA.
Comment 1 Jonathan Robie 2008-05-19 09:32:16 EDT
1.3. Topic Exchange

A Topic exchange is similar to a Direct exchange, but uses keys that contain
multiple words separated by a “.” delimiter. A message producer might create
messages with routing keys like usa.news, usa.weather, europe.news, and

Binding keys for a Topic exchanges can include wildcard characters: a “#”
matches one or more words, a “*” matches a single word. Typical bindings use
binding keys like #.news (all news items), usa.# (all items in the USA), or
usa.weather (all USA weather items). 

Note You need to log in before you can comment on or make changes to this bug.