At the moment I am setting up a Workflow to extract data from my Redis Cache using the Redis Node. The data stored in my Redis db is in a Time Series format using the RedisTimeSeries Module.
Looking through the list of available commands on the Redis node it appears that the RedisTimeSeries Module commands are not available (e.g TS.MGET, TS.MRANGE, etc). When using Redis commands outside of the Redis Time Series Module you end up with the following error: “WRONGTYPE Operation against a key holding the wrong kind of value”
Is there a reason why Losant does not allow for this ? Also, is there a workaround to enable to query my time series from my Redis cache ?
This cache is storing forecasted time series values from a machine leaning model running on Sage maker.
Main reason is, these commands are not part of core Redis and come only with the time series module, and that nobody has asked to have these added - until now!
I will file a ticket to add the Time Series Module commands to the list and will follow up if / when we implement.
As for a workaround - is this an edge workflow interacitng with a Redis database on the device, or do you have some other setup? If you let us know that we may be able to come up with something.
Thank you Dylan for the update. Keep me posted if there a chance Losant would add additional integrations with the Redis Time Series Module — this would be great!
The devices do not directly interact with Redis. Device data is sent into AWS using a Lambda function and then a model produces an output into Redis.
The goal of the workflow I am working on now is to receive time series data (predictions) from a Redis db and then compare those values (predictions) with new data coming from Losant devices.
If all else fails I might be able to store my data in Redis as a more standardized data format that is supported by Losant or use a better an alternative database option that is more compatible with Losant.
Any suggestions would be great as well!
For a workaround, is there any reason you couldn’t use Lambda to get the values out of the Redis database? That’s the best suggestion I have until we add first-class support for the commands in the Redis Node.
Yeah that that also seems like a great option. I have no issue in making a lambda function as a workaround for now. Thanks!