You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Omit feature flag `rabbit_mqtt_qos0_queue` in the MQTT docs since this
feature flag has become required. This makes the docs easier to read.
There is no point in describing the behaviour of this feature flag being
disabled if it cannot be disabled in RabbitMQ 4.1.
Copy file name to clipboardExpand all lines: docs/mqtt.md
+5-6Lines changed: 5 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -116,7 +116,7 @@ By default, the plugin creates a classic queue.
116
116
The plugin can be configured to create quorum queues (instead of classic queues) for subscribers whose MQTT session lasts longer than their MQTT network connection.
117
117
This is explained in section [Quorum Queues](#quorum-queues).
118
118
119
-
If [feature flag](./feature-flags)`rabbit_mqtt_qos0_queue` is enabled, the plugin creates an MQTT QoS 0 queue for QoS 0 subscribers whose MQTT session last as long as their MQTT network connection.
119
+
The plugin creates an MQTT QoS 0 queue for QoS 0 subscribers whose MQTT session last as long as their MQTT network connection.
120
120
This is explained in section [MQTT QoS 0 queue type](#qos0-queue-type).
121
121
122
122
### [Queue Properties](./queues#properties) and [Arguments](./queues#optional-arguments)
@@ -195,13 +195,12 @@ Quorum queues are a great fit for a few (hundreds) longer lived clients that act
195
195
196
196
## MQTT QoS 0 queue type {#qos0-queue-type}
197
197
198
-
The MQTT plugin creates an MQTT QoS 0 queue if the following three conditions are met:
198
+
The MQTT plugin creates an MQTT QoS 0 queue if the following two conditions are met:
199
199
200
-
1.[Feature flag](./feature-flags)`rabbit_mqtt_qos0_queue` is enabled.
201
-
2. The MQTT client subscribes with QoS 0.
202
-
3. The MQTT 5.0 client connects with a [Session Expiry Interval](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901048) of 0, or the MQTT 3.1.1 client connects with CleanSession set to 1.
200
+
1. The MQTT client subscribes with QoS 0.
201
+
2. The MQTT 5.0 client connects with a [Session Expiry Interval](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901048) of 0, or the MQTT 3.1.1 client connects with CleanSession set to 1.
203
202
204
-
The third condition means that the MQTT session lasts only as long as the network connection.
203
+
The second condition means that the MQTT session lasts only as long as the network connection.
205
204
206
205
The MQTT QoS 0 queue type can be thought of as a “pseudo” or “virtual” queue:
207
206
It is very different from the other queue types (classic queues, quorum queues, and streams) in the sense that this new queue type is neither a separate Erlang process nor does it store messages on disk.
Copy file name to clipboardExpand all lines: versioned_docs/version-4.1/mqtt.md
+5-6Lines changed: 5 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -116,7 +116,7 @@ By default, the plugin creates a classic queue.
116
116
The plugin can be configured to create quorum queues (instead of classic queues) for subscribers whose MQTT session lasts longer than their MQTT network connection.
117
117
This is explained in section [Quorum Queues](#quorum-queues).
118
118
119
-
If [feature flag](./feature-flags)`rabbit_mqtt_qos0_queue` is enabled, the plugin creates an MQTT QoS 0 queue for QoS 0 subscribers whose MQTT session last as long as their MQTT network connection.
119
+
The plugin creates an MQTT QoS 0 queue for QoS 0 subscribers whose MQTT session last as long as their MQTT network connection.
120
120
This is explained in section [MQTT QoS 0 queue type](#qos0-queue-type).
121
121
122
122
### [Queue Properties](./queues#properties) and [Arguments](./queues#optional-arguments)
@@ -195,13 +195,12 @@ Quorum queues are a great fit for a few (hundreds) longer lived clients that act
195
195
196
196
## MQTT QoS 0 queue type {#qos0-queue-type}
197
197
198
-
The MQTT plugin creates an MQTT QoS 0 queue if the following three conditions are met:
198
+
The MQTT plugin creates an MQTT QoS 0 queue if the following two conditions are met:
199
199
200
-
1.[Feature flag](./feature-flags)`rabbit_mqtt_qos0_queue` is enabled.
201
-
2. The MQTT client subscribes with QoS 0.
202
-
3. The MQTT 5.0 client connects with a [Session Expiry Interval](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901048) of 0, or the MQTT 3.1.1 client connects with CleanSession set to 1.
200
+
1. The MQTT client subscribes with QoS 0.
201
+
2. The MQTT 5.0 client connects with a [Session Expiry Interval](https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901048) of 0, or the MQTT 3.1.1 client connects with CleanSession set to 1.
203
202
204
-
The third condition means that the MQTT session lasts only as long as the network connection.
203
+
The second condition means that the MQTT session lasts only as long as the network connection.
205
204
206
205
The MQTT QoS 0 queue type can be thought of as a “pseudo” or “virtual” queue:
207
206
It is very different from the other queue types (classic queues, quorum queues, and streams) in the sense that this new queue type is neither a separate Erlang process nor does it store messages on disk.
0 commit comments