You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by "Petrenko, Vadim" <va...@ns.nl> on 2020/10/12 14:33:25 UTC
Qpid topic wildcard aggregation
Dear Qpid developers,
We have a mesh of interior routers with an incoming edge router and an outgoing edge router.
We would like to send messages to several different topics on the incoming edge router, e.g.:
topic1.sensor1
topic1.sensor2
topic1.sensor3
And then consume messages from all sensors using wildcards in the topic name on the outgoing edge router, e.g.: topic1.*
So that a single receiver would receive all messages sent to the above 3 topics.
We have tried different combinations, like # instead of * and other possibilities existing in ActiveMQ, but to no avail.
Is this something Qpid supports? I’ve seen a section in the docs about using wildcards, but it looks more related to configuring routers.
Could you please clarify this?
Thank you in advance.
________________________________
Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor (gebruik door) de geadresseerde. De e-mail kan persoonlijke of vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail (en eventuele bijlagen) te vernietigen.
Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
RE: Qpid topic wildcard aggregation
Posted by "Petrenko, Vadim" <va...@ns.nl>.
Thank you guys, now it's clear.
-----Original Message-----
From: Ken Giusti <kg...@redhat.com>
Sent: dinsdag 13 oktober 2020 15:12
To: users <us...@qpid.apache.org>
Subject: Re: Qpid topic wildcard aggregation
Unfortunately the dispatch router does not support subscriptions to wildcarded addresses. Address patterns (wildcards) are only used for address configuration - setting address attributes such as distribution treatment, priority, etc.
________________________________
Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor (gebruik door) de geadresseerde. De e-mail kan persoonlijke of vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail (en eventuele bijlagen) te vernietigen.
Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
Re: Qpid topic wildcard aggregation
Posted by Ken Giusti <kg...@redhat.com>.
On Tue, Oct 13, 2020 at 6:00 AM Petrenko, Vadim <va...@ns.nl>
wrote:
> Hi Robbie,
>
> Yes, my question was about the qpid dispatch-router-only setup. Can we use
> topic wildcard subscriptions there (topic1.*)?
>
> I used ActiveMQ as an example of desired functionality. We could
> eventually introduce brokers in this picture, but prefer to avoid this and
> have a qpid dispatch-router mesh only, to stay as lean as possible.
>
> The configuration is quite simple, it's a test setup:
>
> Edge publisher (address section):
> address {
> prefix: my_queue
> waypoint: yes
> distribution: multicast
> }
> Edge consumer (address section):
> address {
> prefix: my_queue
> waypoint: yes
> distribution: multicast
> }
>
> Interior routers have only connectors and listeners defined, there are no
> linkRoutes or autolinks in this config. All this works perfectly with
> qpid-jms examples. The only question is whether we can use wildcard
> subscriptions ;)
>
>
Unfortunately the dispatch router does not support subscriptions to
wildcarded addresses. Address patterns (wildcards) are only used for
address configuration - setting address attributes such as distribution
treatment, priority, etc.
> Thanks,
> Vadim.
>
> -----Original Message-----
> From: Robbie Gemmell <ro...@gmail.com>
> Sent: dinsdag 13 oktober 2020 11:17
> To: users@qpid.apache.org
> Subject: Re: Qpid topic wildcard aggregation
>
> You mentioned ActiveMQ, was that just in relation to its particular syntax
> or are you also using the broker with the routers? Essentially, can you
> clarify if the setup is router-only or not? What are your address[ +
> linkRoute + autoLink] settings like generally on the routers currently?
> That might help someone with more knowledge answer better.
>
> (I think the answer is that the router does not support 'topic like'
> wildcard subscriptions on its own directly, but could perhaps together
> with a broker that does)
>
> On Mon, 12 Oct 2020 at 15:44, Petrenko, Vadim <va...@ns.nl>
> wrote:
> >
> > Dear Qpid developers,
> >
> > We have a mesh of interior routers with an incoming edge router and an
> outgoing edge router.
> > We would like to send messages to several different topics on the
> incoming edge router, e.g.:
> >
> > topic1.sensor1
> > topic1.sensor2
> > topic1.sensor3
> >
> > And then consume messages from all sensors using wildcards in the
> > topic name on the outgoing edge router, e.g.: topic1.* So that a single
> receiver would receive all messages sent to the above 3 topics.
> >
> > We have tried different combinations, like # instead of * and other
> possibilities existing in ActiveMQ, but to no avail.
> >
> > Is this something Qpid supports? I’ve seen a section in the docs about
> using wildcards, but it looks more related to configuring routers.
> > Could you please clarify this?
> >
> > Thank you in advance.
> >
> >
> > ________________________________
> >
> > Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor
> (gebruik door) de geadresseerde. De e-mail kan persoonlijke of
> vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging,
> verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en
> eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u
> niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene
> die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail
> (en eventuele bijlagen) te vernietigen.
> >
> > Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional
> commands, e-mail: users-help@qpid.apache.org
>
>
> ________________________________
>
> Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor
> (gebruik door) de geadresseerde. De e-mail kan persoonlijke of
> vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging,
> verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en
> eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u
> niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene
> die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail
> (en eventuele bijlagen) te vernietigen.
>
> Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
--
-K
RE: Qpid topic wildcard aggregation
Posted by "Petrenko, Vadim" <va...@ns.nl>.
Hi Robbie,
Yes, my question was about the qpid dispatch-router-only setup. Can we use topic wildcard subscriptions there (topic1.*)?
I used ActiveMQ as an example of desired functionality. We could eventually introduce brokers in this picture, but prefer to avoid this and have a qpid dispatch-router mesh only, to stay as lean as possible.
The configuration is quite simple, it's a test setup:
Edge publisher (address section):
address {
prefix: my_queue
waypoint: yes
distribution: multicast
}
Edge consumer (address section):
address {
prefix: my_queue
waypoint: yes
distribution: multicast
}
Interior routers have only connectors and listeners defined, there are no linkRoutes or autolinks in this config. All this works perfectly with qpid-jms examples. The only question is whether we can use wildcard subscriptions ;)
Thanks,
Vadim.
-----Original Message-----
From: Robbie Gemmell <ro...@gmail.com>
Sent: dinsdag 13 oktober 2020 11:17
To: users@qpid.apache.org
Subject: Re: Qpid topic wildcard aggregation
You mentioned ActiveMQ, was that just in relation to its particular syntax or are you also using the broker with the routers? Essentially, can you clarify if the setup is router-only or not? What are your address[ + linkRoute + autoLink] settings like generally on the routers currently? That might help someone with more knowledge answer better.
(I think the answer is that the router does not support 'topic like'
wildcard subscriptions on its own directly, but could perhaps together with a broker that does)
On Mon, 12 Oct 2020 at 15:44, Petrenko, Vadim <va...@ns.nl> wrote:
>
> Dear Qpid developers,
>
> We have a mesh of interior routers with an incoming edge router and an outgoing edge router.
> We would like to send messages to several different topics on the incoming edge router, e.g.:
>
> topic1.sensor1
> topic1.sensor2
> topic1.sensor3
>
> And then consume messages from all sensors using wildcards in the
> topic name on the outgoing edge router, e.g.: topic1.* So that a single receiver would receive all messages sent to the above 3 topics.
>
> We have tried different combinations, like # instead of * and other possibilities existing in ActiveMQ, but to no avail.
>
> Is this something Qpid supports? I’ve seen a section in the docs about using wildcards, but it looks more related to configuring routers.
> Could you please clarify this?
>
> Thank you in advance.
>
>
> ________________________________
>
> Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor (gebruik door) de geadresseerde. De e-mail kan persoonlijke of vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail (en eventuele bijlagen) te vernietigen.
>
> Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org
________________________________
Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor (gebruik door) de geadresseerde. De e-mail kan persoonlijke of vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail (en eventuele bijlagen) te vernietigen.
Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
Re: Qpid topic wildcard aggregation
Posted by Robbie Gemmell <ro...@gmail.com>.
You mentioned ActiveMQ, was that just in relation to its particular
syntax or are you also using the broker with the routers? Essentially,
can you clarify if the setup is router-only or not? What are your
address[ + linkRoute + autoLink] settings like generally on the
routers currently? That might help someone with more knowledge answer
better.
(I think the answer is that the router does not support 'topic like'
wildcard subscriptions on its own directly, but could perhaps together
with a broker that does)
On Mon, 12 Oct 2020 at 15:44, Petrenko, Vadim <va...@ns.nl> wrote:
>
> Dear Qpid developers,
>
> We have a mesh of interior routers with an incoming edge router and an outgoing edge router.
> We would like to send messages to several different topics on the incoming edge router, e.g.:
>
> topic1.sensor1
> topic1.sensor2
> topic1.sensor3
>
> And then consume messages from all sensors using wildcards in the topic name on the outgoing edge router, e.g.: topic1.*
> So that a single receiver would receive all messages sent to the above 3 topics.
>
> We have tried different combinations, like # instead of * and other possibilities existing in ActiveMQ, but to no avail.
>
> Is this something Qpid supports? I’ve seen a section in the docs about using wildcards, but it looks more related to configuring routers.
> Could you please clarify this?
>
> Thank you in advance.
>
>
> ________________________________
>
> Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor (gebruik door) de geadresseerde. De e-mail kan persoonlijke of vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail (en eventuele bijlagen) te vernietigen.
>
> Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org