Discrepancy in Count Query Results Between Grafana-Plugins and IoTDB CLI
- Lingua principale
- Java
- Stelle
- 6.4k
- Fork
- 1.2k
- Merge medio
- 1g 23h
- PR unite (30g)
- 115
Descrizione
### 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!
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia riproducendo la discrepanza con i passaggi indicati di IoTDB CLI e Grafana Explore usando le versioni elencate, quindi confronta i risultati di COUNT(DISTINCT()). Traccia il modo in cui l’entry point Grafana-Plugins gestisce la risposta alla query; l’issue è conclusa quando Grafana visualizza lo stesso conteggio della CLI: 2 invece di 0.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- grafana
- Ambito
- databases
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100