apache / apache/iotdb

[Bug] In the latest version of IoTDB, When multiple elements exist under a certain node, there is an error in filtering data using the TIME field.

Abierto
#14,430 1 comentario 0 reacciones 0 asignados Ver en GitHub
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

version 1.3.3 (Build: ad95a7e)

### Describe the bug and provide the minimal reproduce step

```
# statement 1
DROP DATABASE root.db0
CREATE TIMESERIES root.db0.t1.c0 WITH datatype=INT32
INSERT INTO root.db0.t1(timestamp, c0) VALUES (1641024000000, 1);
SELECT * FROM root.db0.t1 WHERE time < 1641024150000 - 1000;

# statement 2
DROP DATABASE root.db1
CREATE TIMESERIES root.db1.t1.c0 INT32;
CREATE TIMESERIES root.db1.t1.c1 INT32;
CREATE TIMESERIES root.db1.t1.c2 WITH datatype=INT32;
INSERT INTO root.db1.t1(timestamp, c2, c1, c0) VALUES (1641024000000, 1, 1, 1);
SELECT * FROM root.db1.t1 WHERE time < 1641024150000 - 1000;
```

### What did you expect to see?

Expected result set for statement 1: **1**

Expected result set for statement 1: **1**

### What did you see instead?

statement 1 returned result set: **1**

statement 2 returned result set: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "SELECT * FROM root.db1.t1 WHERE (time) < 1641024150000 - 1000". executeStatement failed. null

### Anything else?

Dear IoTDB team, Statement 1 and Statement 2 perform the same query, with the only difference being that the data nodes are different. The data node in Statement 2 contains multiple elements. Theoretically, the query results of both should be identical, but an error occurs when executing Statement 2.

### Are you willing to submit a PR?

- [ ] I'm willing to submit a PR!

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Empieza ejecutando las dos reproducciones SQL del issue contra IoTDB versión 1.3.3, comparando los casos de un solo elemento y de múltiples elementos. Sigue la ruta de consulta con filtro TIME para statement 2 y confirma que el fix hace que ambas consultas devuelvan el conjunto de resultados esperado sin INTERNAL_SERVER_ERROR.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
java
Á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
38/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.