I ve only scanned all the above so
I've only scanned all the above so apologies if this has already been asked and answered.
Having created a similar ABR solution for time series data years ago, I have some questions about querying. When you say query billing would be by "rows per query" how is this affected by ABR sampling? If I query 1 months worth of 1Hz data, how many rows will this hit? I guess you'd hit the downsampled rows rather than all 2.6m rows! But how many rows would this be?
The main downside I see to the current query API is that there's no control over read sampling and if you did add that as a feature, it would be super helpful to have a way to find out roughly how many rows a query would hit.
For us it's key for spikes to not get hidden by averaging. So to display downsampled data, we plot at least pixel width number of samples as min/max points with a filled area. This means that the plotted data more closely resembles what you'd see if you plotted every single sample.
2 Replies
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
Makes sense, thanks for the details and docs links!