Why did the latest data value result returned from "order by time desc", "limit 10", "limit 100" are different in Apache IoTDB?

I am now using version 1.1.0 of Apache IoTDB, and when I am executing order by time desc, order by time desc limit 10, and order by time desc limit 100, the latest query results of the time series are different (it should not be like this). When I add limit 10 to the query statement, the first data returned is not the timestamp of the latest data results stored in IoTDB. Is there a bug for this function and how to correct it?

Solution

This bug should already been fixed in new Apache IoTDB versions(for example Version 1.2 and 1.3), so you can update your IoTDB to either versions to solve this error.