Discrepancy in Count Query Results Between Grafana-Plugins and IoTDB CLI
- Vorherrschende Sprache
- Java
- Sterne
- 6.4k
- Forks
- 1.2k
- Ø Merge
- 1 T. 23 Std.
- Gemergte PRs (30 T.)
- 115
Beschreibung
### 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!
Beitragsleitfaden
Rechercherichtung
Beginne damit, die Abweichung mit den gemeldeten IoTDB CLI- und Grafana Explore-Schritten unter Verwendung der aufgeführten Versionen zu reproduzieren und die Ergebnisse von COUNT(DISTINCT()) zu vergleichen. Verfolge, wie der Einstiegspunkt Grafana-Plugins die Abfrageantwort verarbeitet; das Issue ist abgeschlossen, wenn Grafana denselben Count wie die CLI anzeigt: 2 statt 0.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- grafana
- Bereich
- databases
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100