feat(connector): Add mqtt connector #15388
Merged
Task list completed / task-list-completed
succeeded
Mar 13, 2024 in 0s
11 / 11 tasks completed
All tasks have been completed
Details
Required Tasks
| Task | Status |
|---|---|
| MQTT v5 | Completed |
| QoS settings using 0 (At most once) by default | Completed |
| Support for plain TCP and SSL, including client authentication | Completed |
| Retain option for sinks | Completed |
| Data splits when using wildcards. Since it’s not supported by default, the way is achieved is by subscribing to the topics using the wildcard and for each new message received will check if the topic was added to include it on the splits. | Completed |
| I have written necessary rustdoc comments | Completed |
| I have added necessary unit tests and integration tests | Completed |
| I have added test labels as necessary. See details. | Completed |
| I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934). | Completed |
All checks passed in ./risedev check (or alias, ./risedev c) |
Completed |
| My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users) | Completed |
| Why do you want MQTT connector? What do you want to use RisingWave for? | Incomplete |
| How does the MQTT connector work? I think it may be different from message brokers like Kafka, and can lose messages. Is it problematic? | Incomplete |
| Why do you want MQTT connector? What do you want to use RisingWave for? | Incomplete |
| How does the MQTT connector work? I think it may be different from message brokers like Kafka, and can lose messages. Is it problematic? | Incomplete |
Loading