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
It is common for MQTT use cases to distribute data over multiple topics. You might have different subtopics for different devices for example. The MQTT source kamelet supports subscribing to multiple topics by using wildcards but the information about the topic is lost because the MQTT source only reports the body of the MQTT message to the sink. It would be great, if the topic could be included in the body that is reported to the sink.
Example:
You have multiple devices publishing to the topics: /data/deviceId1 /data/deviceId2
...
The MQTT source is able to subscribe to the topic /data/# and it receives all messages. However, the information about which device sent the message is lost.
The text was updated successfully, but these errors were encountered:
It is common for MQTT use cases to distribute data over multiple topics. You might have different subtopics for different devices for example. The MQTT source kamelet supports subscribing to multiple topics by using wildcards but the information about the topic is lost because the MQTT source only reports the body of the MQTT message to the sink. It would be great, if the topic could be included in the body that is reported to the sink.
Example:
You have multiple devices publishing to the topics:
/data/deviceId1
/data/deviceId2
...
The MQTT source is able to subscribe to the topic
/data/#
and it receives all messages. However, the information about which device sent the message is lost.The text was updated successfully, but these errors were encountered: