-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable subtopic support for downstream messages with Pub/Sub messaging infrastructure #3488
Comments
mattkaem
added a commit
to sotec-iot/hono
that referenced
this issue
May 11, 2023
…/Sub messaging infrastructure Enable subtopic support in case Pub/Sub is used as the messaging infrastructure by checking if the topic contains subtopics and rerouting them to the respective Pub/Sub topic (e.g. MQTT topic event/exampleTenant/exampleDevice/subtopic to Pub/Sub topic exampleTenant.event.subtopic). Implement a fallback mechanism in case the subtopic does not exist. In case the subtopic does not exist the message would instead get send to the "main" topic (e.g. telemetry or event). Signed-off-by: matthiask <[email protected]>
mattkaem
added a commit
to sotec-iot/hono
that referenced
this issue
May 11, 2023
…/Sub messaging infrastructure Enable subtopic support in case Pub/Sub is used as the messaging infrastructure by checking if the topic contains subtopics and rerouting them to the respective Pub/Sub topic (e.g. MQTT topic event/exampleTenant/exampleDevice/subtopic to Pub/Sub topic exampleTenant.event.subtopic). Implement a fallback mechanism in case the subtopic does not exist. In case the subtopic does not exist the message would instead get send to the "main" topic (e.g. telemetry or event). Signed-off-by: matthiask <[email protected]>
mattkaem
added a commit
to sotec-iot/hono
that referenced
this issue
May 22, 2023
…/Sub messaging infrastructure Enable subtopic support in case Pub/Sub is used as the messaging infrastructure by checking if the topic contains subtopics and rerouting them to the respective Pub/Sub topic (e.g. MQTT topic event/exampleTenant/exampleDevice/subtopic to Pub/Sub topic exampleTenant.event.subtopic). Implement a fallback mechanism in case the subtopic does not exist. In case the subtopic does not exist the message would instead get send to the "main" topic (e.g. telemetry or event). Signed-off-by: matthiask <[email protected]>
sophokles73
pushed a commit
that referenced
this issue
May 24, 2023
…ng infrastructure Enable subtopic support in case Pub/Sub is used as the messaging infrastructure by checking if the topic contains subtopics and rerouting them to the respective Pub/Sub topic (e.g. MQTT topic event/exampleTenant/exampleDevice/subtopic to Pub/Sub topic exampleTenant.event.subtopic). Implement a fallback mechanism in case the subtopic does not exist. In case the subtopic does not exist the message would instead get send to the "main" topic (e.g. telemetry or event). Signed-off-by: matthiask <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is part of the adaption process in order to qualify Hono as a replacement for Google IoT Core customers. (see #3441, #3442, #3464, #3471)
To our knowledge Hono currently doesnt support the use of subtopics for downstream messages. In order to introduce the state topic as a subtopic of the event topic (see issue #3464), we need to enable the possiblity to send data to subtopics. Since this is a Google IoT Core feature, it might make sense to only implement this for the Pub/Sub messaging infrastructure.
Therefore we propose:
Enable subtopic support in case Pub/Sub is used as the messaging infrastructure by checking if the topic contains subtopics and rerouting them to the respective Pub/Sub topic (e.g. MQTT topic event/exampleTenant/exampleDevice/subtopic to Pub/Sub topic exampleTenant.event.subtopic).
Implement a fallback mechanism in case the subtopic does not exist. In case the subtopic does not exist the message would instead get send to the "main" topic (e.g. telemetry or event).
The text was updated successfully, but these errors were encountered: