[rabbitmq-discuss] Queue federation modifying routing keys in transit

[Simon MacMullen]

Hi. It's expected behaviour - the messages are republished by the 
federation mechanism, which means they need to be published to the 
default exchange with the queue name as routing key.

I see how this is unhelpful though, but I'm not sure of a good way round 
it. We could maybe use http://www.rabbitmq.com/sender-selected.html 
somehow but then we'd need a way to make sure the original routing key 
wasn't used for routing. Hmm.

This doesn't constitute a problem in the exchange federation case 
because we republish with the original routing key since we don't need 
to route to a particular queue.

Cheers, Simon

On 29/11/2013 12:49, Simon Holness wrote:
> Hi all,
>
> We’re just trying out Queue Federation (using 3.2.1) and seeing what
> appears, to us, to be an odd behaviour. I wonder if someone could tell
> us if it’s expected behaviour, a misconfiguration on our part or a bug?
>
> We typically have queues named after the services which connect to them,
> e.g. “my.download.service”
>
> Messages typically have somewhat unrelated routing keys, e.g.
> “download.started”
>
> When we post a “download.started” message to the upstream exchange, the
> message received by the downstream consumer has type
> “my.download.service” (which is promptly rejected because we care about
> message types).
>
> FWIW we tested with exchange federation instead and that all works fine.
>
> Any enlightenment welcome.
>
> Thanks,
>
> Simon Holness
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>