[rabbitmq-discuss] 3.3.x dynamic shovel, delivery-mode?

Laing, Michael michael.laing at nytimes.com
Thu Jun 12 17:19:06 BST 2014

+1 on that.

We will not be able to use dynamic shovels in our proxies and product
clusters until we can set delivery_mode, in our case to 1 as we never
persist messages in the core clusters.

Actually we set user_id too.

This usage is actually long-lived rather than dynamic in the usual sense,
but it is very inconvenient to have to restart to change configuration,
particularly since everything else needed to set up a new vhost in our
environment can be done dynamically.


On Thu, Jun 12, 2014 at 11:29 AM, Simon MacMullen <simon at rabbitmq.com>

> On 11/06/14 15:35, Angelo Turetta wrote:
>> I like very much the new dynamic shovels in 3.3, but I'm missing one key
>> feature: how can I force the delivery-mode of messages in transit?
> At the moment you can't.
>  The old static shovels allowed me to specify:
>> {publish_properties, [{delivery_mode, 2}]},
>> While the new api used to define dynamic ones seems not to allow any
>> publish_properties, or at least there is no docs about it.
> No, there's no equivalent.
> One goal for the dynamic shovel was to be a bit simpler than the static
> shovel, which does make it a bit less flexible.
>  Is it possible to make messages persistent with the help of dynamic
>> shovels? Any chance that default parameters specified for static shovels
>> would apply to dynamic ones?
> Hmm, that's an interesting idea. Alternatively, switching delivery_mode
> might be a common enough thing to be worth special casing, the way we
> already do for exchange and routing key. Hmm.
> Cheers, Simon
> --
> Simon MacMullen
> RabbitMQ, Pivotal
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140612/aaf004c7/attachment.html>

More information about the rabbitmq-discuss mailing list