You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "张洪胤 (Jira)" <ji...@apache.org> on 2022/01/30 08:32:00 UTC
[jira] [Created] (IOTDB-2509) [Merge] when write out of order data, data are different after merge.
张洪胤 created IOTDB-2509:
--------------------------
Summary: [Merge] when write out of order data, data are different after merge.
Key: IOTDB-2509
URL: https://issues.apache.org/jira/browse/IOTDB-2509
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Reporter: 张洪胤
Attachments: 12.5.csv, 13.0.csv, check-config.properties, image-2022-01-30-16-24-45-709.png, image-2022-01-30-16-29-41-688.png, image-2022-01-30-16-30-25-700.png, write-config.properties
First, we use double write mode benchmark to write out of order data into IoTDB 0.12.5 and IoTDB 0.13.0, related benchmark config: write-config.properties(please modify host).
then, we use double point check mode benchmark to check the data between them, related benchmark config: check-config.properties.
And we find there are something wrong happen in benchmark log:
!image-2022-01-30-16-24-45-709.png!
After that, we try to find what's wrong of d_1 in this time, use `./export-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -td /home/xzh -q "select * from root.test.g_0.d_0 where time >= 1541390305000 and time < 1541390805000 order by time desc"` to export data. The data of IoTDB 0.12.5 is 12.5.csv, and the data of IoTDB 0.13.0 is 13.0.csv.
Then we compare them and find there are differences:
!image-2022-01-30-16-29-41-688.png!
!image-2022-01-30-16-30-25-700.png!
It looks like that some line in 0.12.5 has been splited into 2 line in 0.13.0.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)