Added tag rabbitmq_v3_1_0 for changeset e58445bf9569
Quick and dirty riff on the theme of federated queues.
Hack around 'go' arriving before we have started, and use same upstream name.
Further fix to the workaround.
Set purpose, handle another hack on top of a hack.
Supervise the queue links properly, and shift some nomenclature to be a bit more like that of exchange federation.
Represent not_started state better.
Try to do something vaguely sensible for basic.get.
merge stable into default
Move everything out to a proper supervision hierarchy. Trigger queue federation by policy rather than hard coding.
Don't just ignore a policy changing. And note the existence of a clustering bug.
Probably easier just to fix than document in fact.
Allow specifying a different queue name for the upstream, remove use of a fake exchange, start to write tests, remember to sepcify drain.
Disable this test until we are much further along.
A bunch more tests, and a (temporary) fix thus discovered.
Start to abstract the common code from rabbit_federation_link to rabbit_federation_link_util and get rabbit_federation_queue_link to use it too. Thus far: connection setup and shut down. And by extension support status reporting for queue links.
Oops, unbreak tests
Share ack/nack/deliver code with exchange links.
Fix bugs.
Update headers when message forwarded.