This issue is just tracking an idea about how to achieve something in Node-RED. It currently doesn't have a define use-case or specific need. We could use this idea to create an example flow on https://docs.clarify.us (or in the Node-RED libs community).
Because data and meta-data are uploaded in different API calls, and because this calls can be updated out of order, it is possible to split them into different messages and send them to different flows for insertion into Clarify. That this is possible, might not be immidialtey clear to the node users without good documentation or examples.
Possible use-cases for splitting data and meta-data:
For clarity, run meta-data through a separate flow to standardize and enrich it.
Minimize the size and processing complexity of the data messages (i.e. down-sampling flows converting series to data-points before processing don't need to copy/replicate the meta-data).
Protect meta-data flow could a per topic rate-limiter (using either a delay or rbe node) to reduce resource consumption and/or log output.
Presumably works best with moving Input ID to topic as described in #28. However, if not, it is always possible to populate msg.topic with a copy of the information in signal.id when using blocks such as rbe or rate-limit.
This issue is just tracking an idea about how to achieve something in Node-RED. It currently doesn't have a define use-case or specific need. We could use this idea to create an example flow on https://docs.clarify.us (or in the Node-RED libs community).
Because data and meta-data are uploaded in different API calls, and because this calls can be updated out of order, it is possible to split them into different messages and send them to different flows for insertion into Clarify. That this is possible, might not be immidialtey clear to the node users without good documentation or examples.
Possible use-cases for splitting data and meta-data:
Presumably works best with moving Input ID to topic as described in #28. However, if not, it is always possible to populate
msg.topicwith a copy of the information insignal.idwhen using blocks such as rbe or rate-limit.