Hello; I have a question about the Iot Bridge for Snowflake. We are currently building a POC for the customer and we are using Ignition (Edge+Gateway) in combination with Mqtt modules (we want to build a full mqtt connectivity). One future scenario (not well defined at this moment by the customer)) is that some process data needs to be sent from the Mqtt broker (at this moment installed on the Ignition - Distributor) to the Snowflake DBs (the customer is already using Snowflake for other use cases). I watched the webinar related to this Snowflake injector and I got the main idea: the injector will create DB schemas in the Snowflake based on the edge nodes definitions and the DB table will contain (as columns) the individual tag members from the UDTs. In the webinar the use case assumes the UDT has no nesting (no UDT inside another UDT). Our data model contains nested UDTs (e.g PhaseResult is a UDT containing sub multiple UDTs like ParameterResult; the ParameterResult contains some tag data like Average, Min, Max). The question is: if we will publish this kind of data over mqtt sparkplug will the Injector work? What kind of columns it will create for the PhaseResult table? How the Average,Min, Max columns will be created?
Should we change the data model so that the target UDT (e.g. PhaseResult) contains ONLY simple tags for each Parameter result (e.g. Parameter1Avg, Parameter2Max).
Unfortunately at this moment we cannot test with the Snowflake system because we have no test environment for that (we can test till the mqtt broker). I would apreciate any suggestions/feedback you may provide. Thank you
In version 1 of the IoT Bridge for Snowflake, any nested UDT instances will not have separate views created for them. Nested UDT instances will show up in the parent UDT view as JSON payload in their own column. In your example, PhaseResult will have its own view and there will be a column for the nested ParameterResult instance. Any tag changes within the ParameterResult nested instance will show up in JSON form in this separate column in the PhaseResult view.
In version 2 of the IoT Bridge for Snowflake, which is being released this week or next, nested UDT instances will have their own view created with the appropriate columns and all tag changes for those nested instances will show up in their own view fully parsed.