[Bug] export data error
- 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 2.0.5
RH9
### Describe the bug and provide the minimal reproduce step
/usr/local/apache-iotdb-2.0.5/tools/export-data.sh -ft sql -pw '' -sql_dialect table -db nezha -table table -t /tmp/testIotdb/data
error msg:
Exception in thread "main" java.lang.NullPointerException: Cannot invoke "org.apache.iotdb.service.rpc.thrift.TSExecuteStatementResp.getStatus()" because "execResp" is null
at org.apache.iotdb.session.SessionConnection.executeQueryStatement(SessionConnection.java:411)
at org.apache.iotdb.session.Session.executeStatementMayRedirect(Session.java:958)
at org.apache.iotdb.session.Session.executeQueryStatement(Session.java:943)
at org.apache.iotdb.session.TableSession.executeQueryStatement(TableSession.java:57)
at org.apache.iotdb.tool.data.ExportDataTable.exportBySql(ExportDataTable.java:130)
at org.apache.iotdb.tool.data.ExportData.main(ExportData.java:243)
but limit 1000 is success
/usr/local/apache-iotdb-2.0.5/tools/export-data.sh -ft sql -pw '' -sql_dialect table -db nezha -q “select * from table limit 1000” -t /tmp/testIotdb/data
desc table :
CREATE TABLE IF NOT EXISTS table(
time TIMESTAMP TIME,
effect_date TIMESTAMP FIELD,
content TEXT FIELD
);
### What did you expect to see?
Successfully exported
### What did you see instead?
Exception in thread
### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Guía de contribución
Línea de trabajo
Reproduzca el comando export-data.sh que falla en IoTDB 2.0.5 y compárelo con la consulta exitosa usando limit 1000. Comience en SessionConnection.java:411 y siga la llamada a través de Session.java:958, TableSession.java:57 y ExportDataTable.java:130. La tarea estará terminada cuando el export mostrado con el dialecto de tablas se complete correctamente sin la null-response exception.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java, sql
- Área
- databases
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 68/100