![]()
Contents
Cirrus Link Resources
Cirrus Link Website![]()
Contact Us (Sales/Support)![]()
Forum![]()
Cirrus Link Modules Docs for Ignition 7.9.x![]()
Inductive Resources
Ignition User Manual![]()
Knowledge Base Articles![]()
Inductive University![]()
Forum![]()
...
As the data moves from the Ignition Edge device through MQTT Sparkplug and into Snowflake different terminology will be used with the equivalence shown below:
...
These tables are populated by the Snowflake Snowpipe Streaming API as data is streamed in by the IoT bridge.
This table contains information derived from each Sparkplug message
, like the Sparkplug IDs: GroupId, EdgenodeId and DeviceId, the message timestamp, the model / model instance, the raw message payload in JSON, etc.as detailed below
This table contains
inserted date/time, message, message id and topicinformation derived from each MQTT message as detailed below
The Node database contains five tables: SPARKPLUG_DEVICE_MESSAGES, SPARKPLUG_DEVICE_REGISTRY, SPARKPLUG_EDGE_NODE_REGISTRY and SPARKPLUG_TEMPLATE_DEFINITION_REGISTRY
...
Contains contains partially processed data where each row in the table is a single message containing data for each model instance (aka. Device Name)
The IoT Bridge for Snowflake will automatically create a new schema in its “Node” database for every Sparkplug edge node it finds. The Bridge will then create Views within this schema for each model found in the Sparkplug edge node data ingested via the bridge . There are two views per model:
...