Determining what queue type should be used is getting more and more involved.
It can come from four different places:
The client (as an x-queue-type argument value) or the HTTP API
Virtual host metadata
Node-wide default from rabbitmq.conf
If all else fails, the fallback ("classic")
In addition, there are two ways to specify a type:
Clients use shortcuts such as "quorum"
Definitions and many places internally use module names such as rabbit_classic_queue
When a client provides no queue type, validation
should take the defaults (virtual host, global,
and the last resort fallback) into account
instead of considering the type to be "undefined".
* [#11548 Make 'queue.declare' aware of virtual host DQT at validation time (backport #11541)](https://github.com/rabbitmq/rabbitmq-server/pull/11548) has been created for branch `v3.13.x`
DQT = default queue type.
Determining what queue type should be used is getting more and more involved.
It can come from four different places:
x-queue-type
argument value) or the HTTP APIrabbitmq.conf
"classic"
)In addition, there are two ways to specify a type:
"quorum"
rabbit_classic_queue
When a client provides no queue type, validation should take the defaults (virtual host, global, and the last resort fallback) into account instead of considering the type to be "undefined".
References #11457 ##11528.