[rabbitmq-discuss] configuring an header exchange binding in rabbitmq.cfg

[Tom Cellucci]

While the description may have been available in the spec, I suppose it was lost on me that the configuration file itself is somehow an implementation of that spec.  So a couple follow up questions:

* Do all the names / parameters in the specification correspond precisely with syntax in rabbitmq.config?  

* If Exchange to Exchange Bindings are listed in the "extensions" section of the RabbitMQ documentation here: http://www.rabbitmq.com/extensions.html (presumedly non-standard), why would the feature also be present in the specification link you provided?

* A 'how-to' showing exchange-to-exchange binding in the shovel pages would be golden; seems it would be a fairly common scenario.

-Tom

On Nov 11, 2011, at 12:44 AM, Matthias Radestock wrote:

> Tom,
> 
> On 11/11/11 00:28, Tom Cellucci wrote:
>> I'd like to configure an exchange binding, which sadly is not
>> working  like I'd hoped.
> > [...]
>>                                   {'exchange.bind', [
>>                                      {exchange,<<"events_forwarding_exchange">>},
>>                                      {exchange,<<"events_local_exchange">>},
>>                                      {arguments, [
>>                                         {"x-match", longstr, "any"},
>>                                         {"route_to_local", longstr, "true"},
>>                                         {"route_to_dc2", longstr, "true"}
>>                                      ]}
>>                                   ]}
>> 
>> With the above configuration, the broker fails to start and emits the following error:
>> 
>> =INFO REPORT==== 10-Nov-2011::16:03:35 ===
>>     application: rabbitmq_shovel
>>     exited: {{invalid_shovel_configuration,master_events_shovel,
>>                  {invalid_parameter_value,sources,
>>                      {unknown_fields,'exchange.bind',[exchange]}}},
>>              {rabbit_shovel,start,[normal,[]]}}
>>     type: permanent
> 
> The field names need to match what is in the spec. See http://www.rabbitmq.com/amqp-0-9-1-reference.html#exchange.bind - so instead of having two 'exchange' fields you need one 'destination' and one 'source' field.
> 
> Matthias.