Reputation: 350
Why original query reported 301 error after data migration to Apache IoTDB Version 1.0.0?
I just migrated my data from Apache IoTDB Version 0.13.2 to Version 1.0.0. When I tried to execute the original sql query, it failed and reported this 301 error: Declared positions (811) does not match column 0's number of entries (735). I am doing aggregation query on time and device level, does the explanation mean that this error is because my set field did not contain specific value within my queried time period?
I checked the official guide on the official website, but cannot find the relevant information to solve this error. I also cannot change the original query statement due to business needs.
Upvotes: 0
Views: 34
Answers (1)
Reputation: 312
No, this seems to be an error caused by tsfile merging error. You can try to upgrade to Apache IoTDB Version 1.1.1, since this bug should have been fixed in Version 1.0.1 and the afterward versions
Upvotes: 0
Related Questions
- After restarting Apache IoTDB version 1.0.0 cluster, how to restore historical data that has changed to `snapshot` directory?
- After deleting the aligned time series in certain device, why did Apache IoTDB still reported "timeseries under this device are aligned" error?
- How to deal with `unable to fetch schema` error when importing csv of Apache IoTDB?
- Why the previous data cannot be queried when data directory did not change in Apache IoTDB?
- How to check the grammar of time series name to avoid reporting "empty set" when querying in Apache IoTDB?
- Constant values in Apache IoTDB time series data: how to query?
- Why Apache IoTDB reported "Invalid method name" error after startup?
- How to complete data migration without "invalid method name" error from Apache IoTDB Version 0.13.2 to Version 1.0.0?