You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Yuan Tian (Jira)" <ji...@apache.org> on 2023/03/23 02:04:00 UTC
[jira] [Created] (IOTDB-5718) Time order bug while using align by device
Yuan Tian created IOTDB-5718:
--------------------------------
Summary: Time order bug while using align by device
Key: IOTDB-5718
URL: https://issues.apache.org/jira/browse/IOTDB-5718
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: Yuan Tian
Assignee: yang caiyin
Attachments: image-2023-03-23-10-03-24-601.png
1C1D IoTDB
change the following two configuration in iotdb-common.properties
data_region_group_extension_policy=CUSTOM
default_data_region_group_num_per_database=3
Then, execute the following sqls
```
insert into root.db.d1(time,s1) values(2018-08-30T08:00:01.000+08:00, 10);
insert into root.db.d1(time,s1) values(2018-09-30T08:00:01.000+08:00, 10);
insert into root.db.d1(time,s1) values(2018-10-07T08:00:01.000+08:00, 10);
insert into root.db.d1(time,s1) values(2018-10-15T08:00:01.000+08:00, 10);
insert into root.db.d1(time,s1) values(2018-10-25T08:00:01.000+08:00, 10);
insert into root.db.d1(time,s1) values(2018-11-03T08:00:01.000+08:00, 10);
insert into root.db.d1(time,s1) values(2018-11-13T08:00:01.000+08:00, 10);
flush;
```
After inserting the data, you can execute the align by device query and see the wrong time ordering
```
select s1 from root.db.d1 align by device;
```
while we don't add align by device, the result is right.
!image-2023-03-23-10-03-24-601.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)