<div dir="ltr"><div>Hi Bob,</div><br><div class="gmail_quote"><div dir="ltr">On Fri, 18 Jan 2019 at 15:14, Bob Claerhout <<a href="mailto:bob.claerhout@aloxy.io">bob.claerhout@aloxy.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div bgcolor="#FFFFFF"> Hi all,<br> <br> I'm in the dark about the topics and subscriptions in Enmasse.<br> I'm currently using a standard addressspace in Enmasse 0.24.1 and using the documentation from <a class="gmail-m_6983913513413609553moz-txt-link-freetext" href="http://enmasse.io/documentation/0.24.1/openshift/#con-standard-address-space-messaging" target="_blank"> http://enmasse.io/documentation/0.24.1/openshift/#con-standard-address-space-messaging</a>. Also I'm using qpid-bow as the consumer and publisher (<a class="gmail-m_6983913513413609553moz-txt-link-freetext" href="https://github.com/Bynder/qpid-bow" target="_blank">https://github.com/Bynder/qpid-bow</a>).<br> I'm having two questions:<br> My first questions is about the wildcards:<br> <blockquote>The documentation states that:<br> <ul> <li>a/#/b matches a/foo/b, a/bar/b, and a/foo/bar/b </li><li>a/+/b matches a/foo/b and a/bar/b, but would not match a/foo/bar<br> </li></ul> I've created a topic address "addressspace/test".<br> I'm performing my subscriptions using following command: "qb message receive addressspace/test".<br> I'm performing my publications using following command: "qb message send addressspace/test message".<br> <br> When I'm subscribing to "addressspace/test" and publishing to "addressspace/test" the subscriber receives the message.<br> When I'm subscribing to "addressspace/test/foo" and publishing to "addressspace/test/foo" the subscriber receives the message.<br> However, when I'm subscribing to "addressspace/test/+" and publishing to "addressspace/test/foo" the subscriber does not receive the message although stated by the documentation. When I publish to "addressspace/test/+" it is received by the subscriber.<br> Also, when I'm subscribing to "addressspace/test/#" and publishing to "addressspace/test/foo" the subscriber does not receive the message although stated by the documentation. When I publish to "addressspace/test/#" it is received by the subscriber.<br> When I'm subscribing to "addressspace/test.*" and publishing to "addressspace/test.foo" the subscriber also receives the message. I got this from the automated tests.<br> Can somebody point me towards what I'm doing wrong or did I wrongly interpreted the documentation?<br> </blockquote> <br></div></blockquote><div><br></div><div>Unfortunately you are possibly doing nothing wrong, and it is probably a bug. For your topic, which "plan" are you using? Reviewing the configuration it looks like there's a but in EnMasse that for small (pooled) topics the pattern matching is not being correctly applied. For large (sharded) topics the pattern matching configuration looks correct in the code. If you are using a pooled topic, can you re-test with a sharded topic and see if it works for you then? </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"> My second question is about the subscription address.<br> <blockquote>Just verifying my assumptions:<br> Say I have a topic "test" and I create a subscription, called "foo", on topic "test/foo/+" every message on topic "test/foo/[anything]"(if my assumption in the previous question is correct) should be forwarded and stored in the subscription "foo". When a client connects to "foo", it receives all messages in the queue.<br> When I have the same topic "test" and I create an additional subscription, called "bar", on topic "test/foo/bar" every message on topic "test/foo/bar" should be forwarded and stored in both subscription "foo" and "bar". When a client connects to "foo", it will receive all messages to "test/foo/+" including the ones to "test/foo/bar". When a client connects to "bar" it will receive all message to "test/foo/bar".<br> Are my assumptions correct?<br> <br> Additional sub question:<br> I'm trying to create a subscription using following yaml template, is this correct?<br> - kind: Address<br> apiVersion: <a href="http://enmasse.io/v1alpha1" target="_blank">enmasse.io/v1alpha1</a><br> metadata:<br> name: foo<br> spec:<br> address: foo<br> topic: test/foo/+<br> type: topic<br> plan: standard-small-topic<br> </blockquote> <br></div></blockquote><div><br></div><div>I don't believe that subscription addresses currently support subscribing to a pattern (rather only to the root of a topic). I may be wrong, but that is probably an (obvious) enhancement request.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"> Can somebody please clarify these things for me and maybe provide working examples?<br></div></blockquote><div><br></div><div>Hope this helps a little</div><div>-- Rob</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"> Thanks!<br> <br> Bob Claerhout<br> <div class="gmail-m_6983913513413609553moz-signature">-- <br> <br> <div class="gmail-m_6983913513413609553moz-signature"> <table> <tbody> <tr> <td><img src="cid:16861ae3155a8d2f9d21" alt=""></td> <td><b>Bob Claerhout</b><br> Software developer<br> M +32 479 34 84 92<br> The Beacon, Sint-Pietersvliet 7, 2000<br> Antwerp<br> <a href="mailto:bob.claerhout@aloxy.io" target="_blank">bob.claerhout@aloxy.io</a> | <a href="http://www.aloxy.io" target="_blank"> www.aloxy.io</a></td> </tr> </tbody> </table> </div> </div> </div> _______________________________________________<br> enmasse mailing list<br> <a href="mailto:enmasse@redhat.com" target="_blank">enmasse@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/enmasse" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/enmasse</a><br> </blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><span style="color:rgb(136,136,136);font-size:12.8px">______________________________</span><span style="color:rgb(136,136,136);font-size:12.8px">______________________________</span><span style="color:rgb(136,136,136);font-size:12.8px">_________________</span><br style="color:rgb(136,136,136);font-size:12.8px"><br style="color:rgb(136,136,136);font-size:12.8px"><span style="color:rgb(136,136,136);font-size:12.8px">Red Hat GmbH, </span><a href="http://www.de.redhat.com/" style="color:rgb(17,85,204);font-size:12.8px" target="_blank">www.de.redhat.com</a><span style="color:rgb(136,136,136);font-size:12.8px">,</span><br style="color:rgb(136,136,136);font-size:12.8px"><span style="color:rgb(136,136,136);font-size:12.8px">Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,</span><br style="color:rgb(136,136,136);font-size:12.8px"><span style="color:rgb(136,136,136);font-size:12.8px">Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill</span><br></div></div></div>