Open ckim1009 opened 6 months ago
Hi, this is your first issue in IoTDB project. Thanks for your report. Welcome to join the community!
Hi, I think the issue is related with the timezone.
The first timestamp from your Python API result 1 is 1201932040000, which is actually 2008-02-02 14:00:40+08:00
.
You may need to set the timezone manually in you Python code.
Search before asking
Version
Apache IoTDB : 1.2.2 Java : 1.8.0_402 Ubuntu : 20.04.6 LTS
Python : 3.8.3 Apache Iotdb python API : 1.3.0
Describe the bug and provide the minimal reproduce step
The results from executing queries via the Python API and running queries in the CLI environment using start-cli.sh are inconsistent.
While inspecting the results of queries executed in both environments against the data stored in IoTDB, I came across this issue. The format of the stored data is defined as follows: create timeseries root.T_drive.taxi.value with datatype=TEXT.
What did you expect to see?
I expect the same number of query results from both environments.
What did you see instead?
CLI result 1
Python API result 1
CLI result 2
Python API result 2
Anything else?
In result 2, the timestamp 1201944600049 ("2008-02-02T18:30:00.049") is not included in the output of the CLI query. However, when searching with the condition "time = 1201944600049," the corresponding tuple is returned.
I'm curious why the tuple is not returned in the time range query.
Are you willing to submit a PR?