Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions integrations/sources/mqtt.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,26 @@

For example, we create a topic named `iot_data` with the data from various IoT devices at a given timestamp, including temperature, humidity readings, and a status field indicating whether the device is in a normal or abnormal state. For more information to learn about MQTT and get started with it, refer to the [MQTT guide](https://mqtt.org/getting-started/).

<Note>
**Connecting to RabbitMQ with MQTT**

To connect RisingWave to a RabbitMQ instance using the MQTT protocol, you need to enable and configure RabbitMQ's MQTT plugin on the broker side:

1. Enable the MQTT plugin:
```bash
rabbitmq-plugins enable rabbitmq_mqtt
```

2. Set the MQTT v5 feature flag:
```bash
rabbitmqctl enable_feature_flag mqtt_v5
```

3. Once configured, you can connect to RabbitMQ using the MQTT connector as described below.

For more details on RabbitMQ's MQTT support, refer to the [RabbitMQ MQTT documentation](https://www.rabbitmq.com/docs/mqtt).
</Note>

## Ingest data into RisingWave

When creating a source, we have the option to either persist the data in RisingWave using `CREATE TABLE` or use `CREATE SOURCE` while specifying the connection settings and data format.
Expand Down Expand Up @@ -60,10 +80,10 @@
| Field | Notes |
| :----------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| url | **Required**. The URL of the broker to connect to, e.g., tcp://localhost. Must be prefixed with `tcp://`, `mqtt://`, `ssl://`, or `mqtts://` to denote the protocol. `mqtts://` and `ssl://` use native certificates if no CA is specified. |
| qos | **Optional**. The quality of service for publishing messages. Defaults to at\_most\_once. Options include `at_most_once`, `at_least_once`, or `exactly_once`. |

Check warning on line 83 in integrations/sources/mqtt.mdx

View check run for this annotation

Mintlify / Mintlify Validation (risingwavelabs) - vale-spellcheck

integrations/sources/mqtt.mdx#L83

Did you really mean 'qos'?

Check warning on line 83 in integrations/sources/mqtt.mdx

View check run for this annotation

Mintlify / Mintlify Validation (risingwavelabs) - vale-spellcheck

integrations/sources/mqtt.mdx#L83

Did you really mean 'at_most_once'?
| username | **Optional**. Username for the MQTT broker. |
| password | **Optional**. Password for the MQTT broker. |
| client\_prefix | **Optional**. Prefix for the MQTT client ID. Defaults to "risingwave". |

Check warning on line 86 in integrations/sources/mqtt.mdx

View check run for this annotation

Mintlify / Mintlify Validation (risingwavelabs) - vale-spellcheck

integrations/sources/mqtt.mdx#L86

Did you really mean 'risingwave'?
| clean\_start | **Optional**. Determines if all states from queues are removed when the client disconnects.<ul><li>If true, the broker clears all client states upon disconnect;</li><li>If false, the broker retains the client state and resumes pending operations upon reconnection.</li></ul> |
| inflight\_messages | **Optional**. Maximum number of inflight messages. Defaults to 100. |
| max\_packet\_size | **Optional**. The maximum message size for the MQTT client. |
Expand Down
Loading