Discrepancy in Count Query Results Between Grafana-Plugins and IoTDB CLI
- 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
- IoTDB 1.2.2 Standalone
- IoTDB Grafana Plugin 1.0 (Grafana interface)
- Grafana 10.2.2
### Describe the bug and provide the minimal reproduce step
### Problem Description
When executing a `SELECT COUNT(DISTINCT())` query, there's an observed inconsistency in the returned count value between Grafana-Plugins and the IoTDB CLI. While the IoTDB CLI returns the expected and accurate count, the Grafana-Plugins display an incorrect count number.
### IoTDB CLI Result (Correct Count)


### Grafana Explore Query (Incorrect Count)


### Steps to Reproduce
1. Execute the `SELECT COUNT(DISTINCT())` query using IoTDB CLI.
2. Execute the same query using Grafana-Plugins within the Grafana Explore interface.
3. Compare the returned count values.
### What did you expect to see?
### Expected Behavior
The count value returned by Grafana-Plugins should align with the count value retrieved using IoTDB CLI for the same `COUNT(DISTINCT())` query.
### What did you see instead?
### Actual Behavior
During the execution of the SELECT COUNT(DISTINCT()) query using Grafana-Plugins, the returned count value deviates from the expected count. Specifically, the count value displayed in Grafana-Plugins is 0, whereas the accurate count obtained through IoTDB CLI is 2.
### Anything else?
The blurried part of the path are just for obscure sensitive data.
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
Start by reproducing the discrepancy with the reported IoTDB CLI and Grafana Explore steps using the listed versions, comparing the COUNT(DISTINCT()) results. Trace how the Grafana-Plugins entry point handles the query response; the issue is done when Grafana displays the same count as the CLI, 2 rather than 0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100