[Bug] export data error
- Dominant language
- Java
- Stars
- 6.4k
- Forks
- 1.2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 115
Description
### 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!
Contributor guide
Research direction
Reproduce the failing export-data.sh command on IoTDB 2.0.5 and compare it with the successful query using limit 1000. Start at SessionConnection.java:411 and follow the call through Session.java:958, TableSession.java:57, and ExportDataTable.java:130. Done means the shown table-dialect export completes successfully without the null-response exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100