[Bug] iotdb查询问题
- Dominant language
- Java
- Stars
- 6.4k
- Forks
- 1.2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 115
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.
### Version
iotdb1.0.0
### Describe the bug and provide the minimal reproduce step
我们在使用iotdb的select做查询时,有时候查询结果与我们实际的预期结果不一致,但是在查询sql中加上order by time desc或者order by timeseries desc查询到的结果就符合我们的查询结果


### What did you expect to see?
期望可以获得正确的查询结果,或者加上order by 是如何获取到正确结果的,是因为我们查询方式不正确造成的吗?
### What did you see instead?
这种查询结果我们目前无法理解
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
Start by reproducing the reported behavior on IoTDB 1.0.0 with the SELECT query and the variants using `order by time desc` and `order by timeseries desc`, comparing the result with the attached examples. Determine whether the differing results are an ordering issue or an invalid query expectation; done means the behavior is explained and, if incorrect, covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100