You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I only get the last timeseries row instead of all of the data. When setting the RUST_LOG=debug, and looking at the terminal output, I noticed the following SQL run on the influxdb:
Get all entries with Influx query: SELECT * FROM /^.*$/ ORDER BY time DESC LIMIT 1
Where 'limit 1' is limiting the output to 1. I do not find any documentation where the REST API can send the 'limit' in the query. I think adding a selector such as '_limit' similar to '_time' might be helpful.
To reproduce
Start a router with influxdb and rest api
Publish a few measurements via curl command
Try to get all the measurements (it will return only the last one).
System info
Zenoh - zenohd v1.0.0-beta.4 built with rustc 1.75.0 (82e1608df 2023-12-21)
Influx - InfluxDB shell version: 1.6.7~rc0
System - Ubuntu 20.04 - Digital Ocean Droplet
The text was updated successfully, but these errors were encountered:
Describe the bug
I have an InfluxDB running and its relevant plugin running on a Zenoh-router as well as a REST plugin.
From the influxdb-client, I can see that the key-expression has multiple rows for the series in the database. Unfortunately, when I run the following:
curl -g "http://<router-ip>:8000/test/**?_time[..]"
I only get the last timeseries row instead of all of the data. When setting the RUST_LOG=debug, and looking at the terminal output, I noticed the following SQL run on the influxdb:
Where 'limit 1' is limiting the output to 1. I do not find any documentation where the REST API can send the 'limit' in the query. I think adding a selector such as '_limit' similar to '_time' might be helpful.
To reproduce
System info
Zenoh - zenohd v1.0.0-beta.4 built with rustc 1.75.0 (82e1608df 2023-12-21)
Influx - InfluxDB shell version: 1.6.7~rc0
System - Ubuntu 20.04 - Digital Ocean Droplet
The text was updated successfully, but these errors were encountered: