<div dir="ltr"><div>While I could configure the upstreams using HTTP API, I don't think this would be very desirable. It might be good in a scenario where things are very well-defined and you only have a few federated queues, but this is not my case.<br>
</div><div><br></div><div>For each queue I would have to:</div><div>* define a new upstream with desired upstream queue name</div><div>* repeat above for each upstream broker</div><div>* define an upstream set containing the queue-specific upstreams I just created</div>
<div>* define a new policy applying the upstream set to the specific federated queue</div><div><br></div><div>So... on a broker that has 5 upstream brokers, each federated queue would require 5 new upstreams, 1 new upstream set, and 1 new policy. I might have hundreds of federated queues, so this could get rather unwieldy. </div>
<div><br></div><div>To complicate matters, if I ever wanted to add another upstream broker (and I might!), I would then need to detect all of the federated queues somehow, loop through them all creating new queue-specific upstreams, and modify all the upstream sets to add the new upstreams.</div>
<div><br></div><div>On the other hand, if an upstream had a property for applying a regular expression substitution pattern, that would be awesome. Then I could just define the upstream queue as something like "s/(.+)/\1.upstream", and that's it! </div>
<div><br></div><div>I guess this is a feature request then. ;-)</div><div><br></div><div>-Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 19, 2013 at 5:30 PM, Michael Klishin <span dir="ltr"><<a href="mailto:michael.s.klishin@gmail.com" target="_blank">michael.s.klishin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="im"><div class="gmail_extra">2013/11/20 Chris <span dir="ltr"><<a href="mailto:stuff@moesel.net" target="_blank">stuff@moesel.net</a>></span><br>
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Is this possible without having to define a different federation-upstream and policy for every single federated queue?</blockquote></div><br></div></div><div class="gmail_extra">No but you can do what you want via HTTP API and a little bit of custom code:<br>
</div><div class="gmail_extra"><br clear="all"><a href="http://www.rabbitmq.com/management.html#http-api" target="_blank">http://www.rabbitmq.com/management.html#http-api</a><span class="HOEnZb"><font color="#888888"><br>
-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br>
<a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
</font></span></div></div>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>