Discrepancy in Count Query Results Between Grafana-Plugins and IoTDB CLI
- Lenguaje dominante
- Java
- Estrellas
- 6.4k
- Forks
- 1.2k
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 115
Descripción
### 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!
Guía de contribución
Línea de trabajo
Comienza reproduciendo la discrepancia con los pasos indicados de IoTDB CLI y Grafana Explore usando las versiones listadas, y compara los resultados de COUNT(DISTINCT()). Rastrea cómo el punto de entrada Grafana-Plugins gestiona la respuesta de la consulta; la issue estará terminada cuando Grafana muestre el mismo recuento que la CLI: 2 en lugar de 0.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- grafana
- Área
- databases
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100