-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Offset and limit combined with aggregation (group by time) gives incorrect results #6661
Comments
e-dard
added
area/influxql
Issues related to InfluxQL query language
area/queries
and removed
area/influxql
Issues related to InfluxQL query language
labels
May 18, 2016
I think this is caused by #6391. |
jsternberg
added a commit
that referenced
this issue
May 18, 2016
The limit optimization was put into the wrong place and caused only part of the shard to be read when a limit was used. The optimization is possible, but requires a bit of refactoring to the code here so the call iterator is created per series before handed to the limit iterator. Fixes #6661.
jsternberg
added a commit
that referenced
this issue
May 19, 2016
The limit optimization was put into the wrong place and caused only part of the shard to be read when a limit was used. The optimization is possible, but requires a bit of refactoring to the code here so the call iterator is created per series before handed to the limit iterator. Fixes #6661.
Thanks guys! Any realistic chance of a 0.13.1 with the fix soon or should we roll back to 0.12? |
jsternberg
added a commit
that referenced
this issue
May 19, 2016
The limit optimization was put into the wrong place and caused only part of the shard to be read when a limit was used. The optimization is possible, but requires a bit of refactoring to the code here so the call iterator is created per series before handed to the limit iterator. Fixes #6661.
I'm going to try and put together the bugfixes that will go into 0.13.1 soon, but if you need this urgently, I personally would downgrade to 0.12 temporarily until we get 0.13.1 out. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
System info: InfluxDB 0.13.0, Amazon Linux AMI on EC2
Steps to reproduce:
Expected behavior:
Actual behavior:
Step 2:
Step 3:
Step 4:
As you can see, the timestamps are correctly returned according to the limit and offset, but for some reason the count is also affected.
Additional info:
We just migrated from InfluxDB 0.9.5 to 0.13.0. All steps were followed and the migration was a success. The queries were working on 0.9.5 this morning, but not on 0.13.0. We don't know which version in between resulted in the changed behaviour.
Offset and limit gives the expected behaviour when querying the raw data without aggregation, but gives incorrect results when any aggregation function is applied.
The text was updated successfully, but these errors were encountered: