zai
Reputation: 31
Why in Apache IoTDB Version 1.0.1, the results returned using the same `last` command can be alternated?
When using last function to query results in Apache IoTDB Version 1.0.1, the actually returned data is not the latest one, and with the same query statement using last, the results are returned alternately (which should not be the case, should return the same result for one time series). Has anyone encountered the same problem and know how to deal with it?
Upvotes: 0
Views: 14
Answers (1)
Hunter King
Reputation: 375
You can update Apache IoTDB to the latest version (version 1.2 and above). Similar bugs should already be fixed.
Upvotes: 0
Related Questions
- Why Apache IoTDB reported "if certain time series exists" after upgraded to Version 1.0.1?
- Why did the latest data value result returned from "order by time desc", "limit 10", "limit 100" are different in Apache IoTDB?
- For Version 1.2.2 of Apache IoTDB, why did `later request in same group will be redirected` error occurred?
- Why did `show cluster details` returned `INTERNAL_SERVER_ERROR(305)` error when upgrading Apache IoTDB Version from 1.0.1 to 1.2?
- Why the result of querying time series returned blank in Apache IoTDB?
- Why returned false when using booleancheckTimeseriesExists for existed time series in Apache IoTDB?
- How to store "no value" fields in Apache IoTDB to reach query returned results faster?
- How to solve "fetch schema failed" problem in Apache IoTDB Version 1.0.1?
- After updating to Version 1.0.1, how can I successfully use "fill(previous)" to fill blank values in Apache IoTDB?
- Why Apache IoTDB Version 1.0.1 cannot use ip number to connect server?