-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[0.9.5] desc modifier in order clause causes records to be omitted #4944
Comments
Unable to test against nightly as nightly (0.9.6-nightly-3de9b9b) fails to run with 'panic: close of nil channel'. |
This is a duplicate of #4235, which is fixed in 0.9.5. Can you upgrade to that release? |
Still present in 0.9.5.1
|
Does the fix for this not work with existing data? I don't see this on 0.9.5.1 in a sandbox with no existing data but I do see it after upgrading my prod hosts from 0.9.4.2. |
@CVTJNII did you change the storage engine configuration for 0.9.5.1 or are you running the default |
I haven't intentionally tuned the engine, it should be using the defaults. This is my [data] config block:
|
Thanks @CVTJNII, that means you're using the default @corylanou it looks like #4235 might have come back. Any ideas what might be happening? |
I've written an influxdb based persistence service for openHAB openhab/openhab1-addons#3610 .
I've used influxdb 0.9.6.1 from homebrew and before testing I've deleted all influxdb data files and switched to tsm1:
Any hints how to solve this? |
I believe this has been fixed during the query engine refactor. If you still experience this issue, please create a new issue. Thank you. |
When sorting a query by time descending records are not returned. Using a simple test script against a InfluxDB 0.9.4.2 instance which is being constantly updated:
Note that records for 16:48 were returned for the queries without the desc modifier, whereas with the desc modifier the latest time is 15:22: over an hour's worth of records are missing. As the sort order is descending the latest records will be first, so this is not a pagination issue.
The above was generated with the following script, which does it's own time sort to ensure the latest row is printed on unordered queries:
The above was run with measurement set to a single series, however this behavior is seen against /.*/ as well.
The text was updated successfully, but these errors were encountered: