-
Notifications
You must be signed in to change notification settings - Fork 18
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
IoT historical data retrieval #5
Comments
The following minor modification for release 0.2.17, enables dynamic database name:
msg.payload.dbName should be set to dynamic value at the node preceding to cloudant in node. |
This is a good feature to support given the changes to the IoT Platform. Note that by convention, if a configuration property has been set in the node, it should not be possible to override it by a message property. If you want to set it via a message property, the value should be left blank in the node's configuration. That means the logic to handle it should be slightly different to what @oprince proposes, but the basic principle is good. |
The IoT events DB name is built of fixed value prefix + dynamic suffix representing the current time interval. |
Due to IoT enhancement of historical data management, my node-red flow should now retrieve IoT events historical data from Cloudant (not directly from IoT as before). I use 'Cloudant in' node to retrieve that data, and it works fine. As the database name changes over time according to the IoT bucket interval, database name has to be set dynamically.
Would it be possible to enable dynamic database name at node-red 'Cloudant in' node (take the dynamic value from input msg) ?
The text was updated successfully, but these errors were encountered: