[Bug] 别名查询多设备最新值
- 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
别名查询最新值
root.ln_1.tb_6141,root.ln_1.tb_0014
window
1:单网关查最新值1.0.1结果不正确,1.2.0结果正确
2:多网关查询最新值,1.0.1和1.2.0报301错误或者结果不正确
3:flush丢数据
4:创建database深一层查不出数据root.ln_1.tb_6141
linux
1:创建database深一层查不出数据root.ln_1.tb_6141
2:多网关查询最新值偶现301错误,并且结果不正确,结果少
### Describe the bug and provide the minimal reproduce step
别名查询最新值
root.ln_1.tb_6141,root.ln_1.tb_0014
window
1:单网关查最新值1.0.1结果不正确,1.2.0结果正确
2:多网关查询最新值,1.0.1和1.2.0报301错误或者结果不正确
3:flush丢数据
4:创建database深一层查不出数据root.ln_1.tb_6141
linux
1:创建database深一层查不出数据root.ln_1.tb_6141
2:多网关查询最新值偶现301错误,并且结果不正确,结果少
### What did you expect to see?
真确结果
### 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
The issue names no files, tests, or entry points. Start by separating and reproducing the alias latest-value query cases for single and multiple gateways on the listed versions, including flush and nested-database scenarios; done would require consistent expected results without 301 errors or missing data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100