Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Contribution Submission: MQTT v5 Input and Output components

オープン
  • 何か問題がありますか？
#4,635 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
静か
技術スタック
go
領域
data-engineering, stream-processing

調査の方向性

まず CONTRIBUTING.md §3.1.1 と既存の mqtt input コンポーネントおよび output コンポーネントを読み、次に paho.golang ベースで提案されている設定とメタデータの範囲を確認します。完了の条件は、Redpanda が MQTT v5 のサポートが求められていることを確認し、範囲を承認し、新しい mqtt5 コンポーネントの実装およびテストに関する期待事項を定義することです。

索引モデルが issue の本文から書いたものです。

説明

Background

We are evaluating Redpanda Connect for use in our data pipelines, but this use case requires MQTT v5 support, which currently does not exist for Redpanda Connect. Currently only MQTT v3.1.1 is supported via the mqtt input and output using the paho.mqtt.golang library.

Prior Work

There were two prior attempts to contribute MQTT v5 support to Redpanda Connect:

  • PR #2197: Was closed due to withdrawal of the contribution on change from Benthos to Redpanda Connect.
  • PR #3731: Was closed due to unaccepted CLA.

Kafka Connect Equivalent

There is no Kafka Connect equivalent since the Kafka Connect MQTT source connector is also based on an MQTT v3.1.1 paho library.

Proposal

We would like to contribute a new mqtt5 input and output component. Per §3.1.1 of the CONTRIBUTING.md, code written by non-Redpanda engineers needs to be reviewed and scoped by Redpanda. We are opening this issue to ask for comments on two points:

  1. Is an MQTT v5 input and output component still desired/wanted by Redpanda?
  2. Is the following scope properly sized for a MQTT v5 input and output component?

Intended Scope

  • A new, separate mqtt5 input and output component.
  • Written in Go and based on paho.golang. This library is written by the same authors as the mqtt.paho.golang library that is already in use with the mqtt connector.
  • Code structure will mirror the existing mqtt connector where it makes sense.
  • All configuration fields shared with the existing mqtt connector are carried over unchanged
  • New mqtt5 input config options:
Field Notes
session_expiry_interval How long the broker retains session state after disconnect.
receive_maximum Maximum in-flight QoS 1/2 messages the broker may send to this client simultaneously.
maximum_packet_size Maximum packet size this client will accept from the broker.
no_local Subscription option: do not receive messages published by this client.
retain_as_published Subscription option: preserve the retain flag from the original publisher.
retain_handling Subscription option: controls whether retained messages are sent on subscribe.
topic_alias_maximum Maximum number of topic aliases this client will accept from the broker. 0 disables topic aliases.
subscription_identifiers Enables the use of subscription identifiers by the client.
will_* Full v5 will message config.
  • Metadata set by the mqtt5 input:
Metadata key Source
mqtt5_user_properties_<key> User Properties from the PUBLISH packet. If a key appears only once, it is stored as-is.
mqtt5_user_properties_<key>_<idx> User Properties from the PUBLISH packet can have the same key multiple times. If this happens they receive a zero-based index as a suffix
mqtt5_content_type Content Type
mqtt5_payload_format_indicator Payload Format Indicator
mqtt5_response_topic Response Topic
mqtt5_correlation_data Correlation Data
mqtt5_subscription_identifier Subscription identifier sent by the broker
  • New mqtt5 output config options:
Field Notes
session_expiry_interval How long the broker retains session state after disconnect.
message_expiry_interval Per-message TTL. Broker drops the message if undelivered before expiry.
topic_alias_maximum Maximum number of topic aliases this client will use when publishing. 0 disables topic aliases.
will_* Full v5 will message config.
  • Metadata read by the mqtt5 output:
Metadata key Written to
mqtt5_user_properties_<key> User Properties on the PUBLISH packet. Plain keys (mqtt5_user_properties_<key>) are written as single entries. Indexed keys (mqtt5_user_properties_<key>_0, _1, etc.) are reassembled into multiple User Properties with the same key, preserving order.
mqtt5_content_type Content Type
mqtt5_payload_format_indicator Payload Format Indicator
mqtt5_response_topic Response Topic
mqtt5_correlation_data Correlation Data
  • Other MQTT v5 Behavior:
    • Shared Subscriptions are supported by the underlying library.
    • Reason codes will be surfaced in error messages.
    • Server-initiated DISCONNECT is handled by the underlying library.
主要言語
Go
スター
8.8k
フォーク
975
平均マージ
3日 22時間
マージ済み PR（30日）
85

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

redpanda-data/connect のほかの issue

redpanda-data/connect の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。