[rabbitmq-discuss] Impact of Updating Queue Parameters on Queued Messages

[Richard Raseley]

Follow-up question:

There doesn't seem to be a lot in the policy documentation about the
available definitions for (specifically) the DLX policies. Am I correct in
assuming there is also a 'dead-letter-routing-key' definition that I can
use for the expected effect?

If yes, is it preferred that these be defined in the same policy or
separate policies with different priorities?

Regards,

Richard


On Tue, Dec 17, 2013 at 10:44 AM, Richard Raseley <richard at raseley.com>wrote:

> Thank you for your reply.
>
> I will review the policy documentation and go that route.
>
> Regards,
>
> Richard
>
>
>
> On Tue, Dec 17, 2013 at 10:26 AM, Simon MacMullen <simon at rabbitmq.com>wrote:
>
>> On 17/12/2013 18:15, Richard Raseley wrote:
>>
>>> A) The messages are purged, the queue is deleted and recreated with the
>>> new parameters.
>>>
>>> B) The messages are preserved and the queue's parameters are just
>>> updated.
>>>
>>> C) Something else?
>>>
>>
>> C) The messages are preserved and the queue's arguments are *not* updated
>> (i.e. the definition for that queue is ignored). Queue arguments never
>> change; the import / export definitions feature does not change that.
>>
>> If you want to add a DLX to an existing queue you can do that with
>> policies in 3.2.x: see "Configuration using policy" under
>> http://www.rabbitmq.com/dlx.html
>>
>> Cheers, Simon
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131217/0b7b1aea/attachment.html>