Documentation clarification about transient_nonexcl_queues feature deprecation #12972
-
Is your feature request related to a problem? Please describe.Per comments #12802 (comment) We could deduce that after deprecation, only classic exclusive queues will be supported. As the queue property is "durable:true" and not "transient:false" the affected queue types should be explicitly documented. Describe the solution you'd likeDescribe the feature flag in https://www.rabbitmq.com/docs/feature-flags . Describe alternatives you've consideredNo response Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
@Tazmaniac the docs are open source, so anyone can edit them. However, there are several factually incorrect claims in what you expect us to document. The term "transient" is used in section dedicated to queue durability. In most client libraries Non-exclusive, transient/non-durable classic queues are still supported, and there are no plans to remove them in 4.1.0. Finally, the combination of Feature flags cannot be disabled once enabled. You will have to enable all feature flags eventually, there is no way around it, if you plan on upgrading RabbitMQ. |
Beta Was this translation helpful? Give feedback.
-
I will not document any queue properties in the feature flags guide. It makes no sense to me. I will add a mention to the Queues guide that non-durable non-exclusive queues are deprecated and will eventually be removed. |
Beta Was this translation helpful? Give feedback.
-
I guess this list of deprecated features can be expanded, too. But deprecated features are not feature flags. They have nothing in common besides the fact that you can enable both. |
Beta Was this translation helpful? Give feedback.
Done rabbitmq/rabbitmq-website@74e96c4