From 5c56ea90a87b06300e18f1b9178fb98c8fd6ba18 Mon Sep 17 00:00:00 2001 From: Reuben Miller Date: Fri, 14 Jul 2023 22:04:23 +0200 Subject: [PATCH] simplifying the description by removing unneeded info * Showing the users that they can register to only a subset topics promotes bad practices when other topic schemas are used. * Removed the comment about the centralized database as this feels too negative and goes outside of the scope of the reference doc Signed-off-by: Reuben Miller --- docs/src/references/mqtt-api.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/docs/src/references/mqtt-api.md b/docs/src/references/mqtt-api.md index e3caf73af00..5ceb3d40ade 100644 --- a/docs/src/references/mqtt-api.md +++ b/docs/src/references/mqtt-api.md @@ -403,19 +403,8 @@ for all possible entity identification topic levels as follows: mosquitto_sub -t 'te/+' -t 'te/+/+' -t 'te/+/+/+' -t 'te/+/+/+/+' ``` -If your use-case has a fixed schema, something like `te/////...` -then you could limit to your subscriptions to a specific set of topics where you expect the registrations as follows: - -```sh -mosquitto_sub -t 'te/+/+' -t 'te/+/+/+/+' -``` - -Where the subscription is limited to just devices at level 3 and services at level 5. - :::note -Thin Edge does not maintain a centralized database of these entities that other components can query. -Instead, the MQTT broker is used to store all the info about entities as retained messages -and components are free to build their own internal entity store from these retained messages with just the relevant data. +The MQTT broker is used as the persistance layer to store the registered entities (assuming the registration messages were published with the MQTT retain flag). ::: ## Data types