[jira] [Created] (IOTDB-846) select failed when query sensor with different datatype
张凌哲 created IOTDB-846: - Summary: select failed when query sensor with different datatype Key: IOTDB-846 URL: https://issues.apache.org/jira/browse/IOTDB-846 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: 张凌哲 Attachments: 3001756DF3F1E04B9DF2EA2B6088EC74.png, error.log When we use cli to query data by sensor. The system fails when we had select data from a sensor with different datatype before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-739) merge has deadlock
张凌哲 created IOTDB-739: - Summary: merge has deadlock Key: IOTDB-739 URL: https://issues.apache.org/jira/browse/IOTDB-739 Project: Apache IoTDB Issue Type: Bug Components: Server Reporter: 张凌哲 Fix For: 0.10.0-SNAPSHOT In online projects, merge usually go into a deallock and block the whole IoTDB system. So we will default close merge in config file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-812) move virtual memtable to merge part
张凌哲 created IOTDB-812: - Summary: move virtual memtable to merge part Key: IOTDB-812 URL: https://issues.apache.org/jira/browse/IOTDB-812 Project: Apache IoTDB Issue Type: Improvement Reporter: 张凌哲 move the virtual memtable from TsFileProcesssor to merge part, controlled in StorageGroupProcessor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-975) Read file error: getChunkMetadataList vs getAllTimeseriesMetadata
张凌哲 created IOTDB-975: - Summary: Read file error: getChunkMetadataList vs getAllTimeseriesMetadata Key: IOTDB-975 URL: https://issues.apache.org/jira/browse/IOTDB-975 Project: Apache IoTDB Issue Type: Bug Reporter: 张凌哲 Attachments: 1599761193405-2-0.tsfile, 1599761193405-2-0.tsfile.mods, 1599761193405-2-0.tsfile.resource, TsFileRead.java Accroding to one file, I can get a chunkMetadata by reader.getChunkMetadataList(path) but when I use reader.getAllTimeseriesMetadata() I cannot get the path above. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-952) Add Latest File Compaction Strategy
张凌哲 created IOTDB-952: - Summary: Add Latest File Compaction Strategy Key: IOTDB-952 URL: https://issues.apache.org/jira/browse/IOTDB-952 Project: Apache IoTDB Issue Type: Improvement Components: Core/Engine Reporter: 张凌哲 Fix For: master branch Current compaction strategy just merge old file, when user write too fast, the compaction can just merge useless data. So we have to develop a compaction strategy that can merge latest file as soon as possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1127) select数学函数报语法错误Msg: 401:
刘珍 created IOTDB-1127:
-
Summary: select数学函数报语法错误Msg: 401:
Key: IOTDB-1127
URL: https://issues.apache.org/jira/browse/IOTDB-1127
Project: Apache IoTDB
Issue Type: Bug
Components: Server
Environment: 0.11.3-SNAPSHOT|
Reporter: 刘珍
create timeseries root.db_1.tab1.salary with datatype=INT64,encoding=PLAIN ;
insert into root.db_1.tab1(time,salary) values(1000,3000);
select salary,sin(salary) from root.db_1.tab1;
Msg: 401: line 1:17 mismatched input '(' expecting \{FROM, ',', '.'}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1128) 按照自然月份的降频聚合查询，结果集中的起始时间不正确
刘珍 created IOTDB-1128: - Summary: 按照自然月份的降频聚合查询，结果集中的起始时间不正确 Key: IOTDB-1128 URL: https://issues.apache.org/jira/browse/IOTDB-1128 Project: Apache IoTDB Issue Type: Bug Environment: 0.11.3-SNAPSHOT Reporter: 刘珍 测试用例，有问题的sql在最后1条： create timeseries root.db_1.tab1.temp with datatype=INT64,encoding=REGULAR ; insert into root.db_1.tab1(time,temp) values(2017-11-01T00:00:00,110101); insert into root.db_1.tab1(time,temp) values(2017-11-01T01:00:00,110102); insert into root.db_1.tab1(time,temp) values(2017-11-01T02:00:00,110103); insert into root.db_1.tab1(time,temp) values(2017-11-01T03:00:00,110104); insert into root.db_1.tab1(time,temp) values(2017-11-01T04:00:00,110105); insert into root.db_1.tab1(time,temp) values(2017-11-01T05:00:00,110106); insert into root.db_1.tab1(time,temp) values(2017-11-01T00:00:00,110101); insert into root.db_1.tab1(time,temp) values(2017-11-01T01:00:00,110102); insert into root.db_1.tab1(time,temp) values(2017-11-01T02:00:00,110103); insert into root.db_1.tab1(time,temp) values(2017-11-01T03:00:00,110104); insert into root.db_1.tab1(time,temp) values(2017-11-01T04:00:00,110105); insert into root.db_1.tab1(time,temp) values(2017-11-01T05:00:00,110106); insert into root.db_1.tab1(time,temp) values(2017-11-02T00:00:00,110201); insert into root.db_1.tab1(time,temp) values(2017-11-02T01:00:00,110202); insert into root.db_1.tab1(time,temp) values(2017-11-02T02:00:00,110203); insert into root.db_1.tab1(time,temp) values(2017-11-02T03:00:00,110204); insert into root.db_1.tab1(time,temp) values(2017-11-02T04:00:00,110205); insert into root.db_1.tab1(time,temp) values(2017-11-02T05:00:00,110206); insert into root.db_1.tab1(time,temp) values(2017-11-03T00:00:00,110301); insert into root.db_1.tab1(time,temp) values(2017-11-03T01:00:00,110302); insert into root.db_1.tab1(time,temp) values(2017-11-03T02:00:00,110303); insert into root.db_1.tab1(time,temp) values(2017-11-03T03:00:00,110304); insert into root.db_1.tab1(time,temp) values(2017-11-03T04:00:00,110305); insert into root.db_1.tab1(time,temp) values(2017-11-03T05:00:00,110306); insert into root.db_1.tab1(time,temp) values(2017-11-04T00:00:00,110401); insert into root.db_1.tab1(time,temp) values(2017-11-04T01:00:00,110402); insert into root.db_1.tab1(time,temp) values(2017-11-04T02:00:00,110403); insert into root.db_1.tab1(time,temp) values(2017-11-04T03:00:00,110404); insert into root.db_1.tab1(time,temp) values(2017-11-04T04:00:00,110405); insert into root.db_1.tab1(time,temp) values(2017-11-04T05:00:00,110406); select count(temp), max_value(temp) from root.db_1.tab1 group by ([2017-11-01T00:00:00, 2017-11-05T03:18:10.000+08:00),1d); select count(temp), max_value(temp) from root.db_1.tab1 group by ([2017-11-01T00:00:00, 2017-11-05T03:18:10.000+08:00),3h,1d); 按照自然月份的降频聚合查询 insert into root.db_1.tab1(time,temp) values(2017-12-04T00:00:00,110401); insert into root.db_1.tab1(time,temp) values(2017-12-04T01:00:00,110402); insert into root.db_1.tab1(time,temp) values(2017-12-04T02:00:00,110403); insert into root.db_1.tab1(time,temp) values(2017-12-04T03:00:00,110404); insert into root.db_1.tab1(time,temp) values(2017-12-04T04:00:00,110405); insert into root.db_1.tab1(time,temp) values(2017-12-04T05:00:00,110406); insert into root.db_1.tab1(time,temp) values(2018-01-04T00:00:00,110401); insert into root.db_1.tab1(time,temp) values(2018-01-04T01:00:00,110402); insert into root.db_1.tab1(time,temp) values(2018-01-04T02:00:00,110403); insert into root.db_1.tab1(time,temp) values(2018-01-04T03:00:00,110404); insert into root.db_1.tab1(time,temp) values(2018-01-04T04:00:00,110405); insert into root.db_1.tab1(time,temp) values(2018-01-04T05:00:00,110406); insert into root.db_1.tab1(time,temp) values(2018-01-04T06:00:00,110407); insert into root.db_1.tab1(time,temp) values(2018-02-04T00:00:00,110401); insert into root.db_1.tab1(time,temp) values(2018-02-04T01:00:00,110402); insert into root.db_1.tab1(time,temp) values(2018-02-04T02:00:00,110403); insert into root.db_1.tab1(time,temp) values(2018-02-04T03:00:00,110404); insert into root.db_1.tab1(time,temp) values(2018-02-04T04:00:00,110405); insert into root.db_1.tab1(time,temp) values(2018-02-04T05:00:00,110406); select count(temp), max_value(temp) from root.db_1.tab1 where time > 2017-11-01T00:00:00 group by ([2017-11-01T00:00:00,2018-02-04T05:00:00),1mo, 2mo); +-+--+--+ | Time|count(root.db_1.tab1.temp)|max_value(root.db_1.tab1.temp)| +-+--+--+ |2017-11-01T00:00:00.000+08:00| 23| 110406| |2017-12-31T00:00:00.000+08:00| 7| 110407| +-+--+--+ Total line number = 2 2017-12-31T00:00:00.000+08:00这个起始时间不正确，应该是2018-01-01 -- This mess
[jira] [Created] (IOTDB-1124) SHOW LATEST TIMESERIES显示顺序不正确
刘珍 created IOTDB-1124: - Summary: SHOW LATEST TIMESERIES显示顺序不正确 Key: IOTDB-1124 URL: https://issues.apache.org/jira/browse/IOTDB-1124 Project: Apache IoTDB Issue Type: Bug Components: Server Environment: version 0.11.3-SNAPSHOT Reporter: 刘珍 Attachments: image-2021-01-25-16-22-14-827.png, image-2021-01-25-16-22-52-738.png 复现流程： cli连接IoTDB每次执行1条SQL： create timeseries root.db_1.tab1.status with datatype=BOOLEAN,encoding=PLAIN ; create timeseries root.db_1.tab2.temperature with datatype=FLOAT,encoding=PLAIN ; create timeseries root.db_1.tab3.hardware with datatype=TEXT,encoding=PLAIN ; create timeseries root.db_1.tab4.price with datatype=DOUBLE,encoding=PLAIN ; create timeseries root.db_1.tab5.age with datatype=INT32,encoding=REGULAR ; create timeseries root.db_1.tab6.salary with datatype=INT64,encoding=REGULAR ; SHOW LATEST TIMESERIES; 结果为： 最近插入时间戳在结果集下面，有序。 !image-2021-01-25-16-22-52-738.png! 再执行 create timeseries root.db_2.tab0.salary with datatype=INT64,encoding=REGULAR ; SHOW LATEST TIMESERIES; --查询结果有序 create timeseries root.db_0.tab0.salary with datatype=INT64,encoding=REGULAR ; SHOW LATEST TIMESERIES; !image-2021-01-25-16-22-14-827.png! 最近插入的时间戳在结果集的第一行，乱序。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1125) set ttl 与flush一起使用，顺序tsfile被delete导致查询Msg: 500: bitIndex < 0: -2147483648
刘珍 created IOTDB-1125: - Summary: set ttl 与flush一起使用，顺序tsfile被delete导致查询Msg: 500: bitIndex < 0: -2147483648 Key: IOTDB-1125 URL: https://issues.apache.org/jira/browse/IOTDB-1125 Project: Apache IoTDB Issue Type: Bug Components: Server Reporter: 刘珍 Attachments: image-2021-01-25-18-13-30-909.png, image-2021-01-25-18-13-34-397.png, image-2021-01-25-18-15-40-631.png 干净的IoTDB数据库 create timeseries root.db_0.tab0.salary with datatype=INT64,encoding=REGULAR ; set ttl to root.db_0 10; --过期时间100秒 insert 2条记录，时间为当前时间 insert into root.db_0.tab0(time ,salary) values(2021-01-25T18:01:01.000+08:00,1200); insert into root.db_0.tab0(time ,salary) values(2021-01-25T18:01:02.000+08:00,1200); 执行查询，可以查询到insert的2条记录。 select * from root.db_0.tab0; !image-2021-01-25-18-13-34-397.png! 大概100秒后再次执行查询，查询结果为空。过期的记录不可见，表现正确。 执行 FLUSH 可以看到data/data/sequence/root.db_0/0下的tsfile文件消失 unset ttl to root.db_0; 再次执行查询 select * from root.db_0.tab0; 查询结果为空，应该可以查询到，因为已经取消ttl。 delete from root.db_0.tab0; insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:01.000+08:00,1200); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:02.000+08:00,1100); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:03.000+08:00,1000); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:04.000+08:00,2200); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:05.000+08:00,1300); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:06.000+08:00,1400); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:07.000+08:00,1500); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:08.000+08:00,1600); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:09.000+08:00,1700); insert into root.db_0.tab0(time ,salary) values(2021-01-25T17:36:10.000+08:00,1800); flush; select * from root.db_0.tab0; 报错 !image-2021-01-25-18-15-40-631.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1130) select * .. .group by 不报错
刘珍 created IOTDB-1130: - Summary: select * .. .group by 不报错 Key: IOTDB-1130 URL: https://issues.apache.org/jira/browse/IOTDB-1130 Project: Apache IoTDB Issue Type: Bug Environment: 0.11.3-SNAPSHOT Reporter: 刘珍 select * from root.group_0.d_0 group by ([2018-09-20T00:00:00.000+08:00, 2018-09-30T00:00:00.000+08:00),1d) 不报错。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1444) Building C++ Client : Fatal error: Navigation Timeout Exceeded: 5000ms exceeded
刘珍 created IOTDB-1444:
-
Summary: Building C++ Client : Fatal error: Navigation Timeout
Exceeded: 5000ms exceeded
Key: IOTDB-1444
URL: https://issues.apache.org/jira/browse/IOTDB-1444
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Others
Affects Versions: 0.12.0
Reporter: 刘珍
Attachments: image-2021-06-18-11-55-17-743.png
master 0616 / 699f866fb73d81c6d35ad6b401ceceb2499decbf
Author: J.J. Liu
Date: Wed Jun 16 22:58:17 2021 +0800
Fix Cpp example not release query dataset bug (#3419)
Running maven command in IoTDB root directory:
mvn package -P compile-cpp -pl example/client-cpp-example -am -DskipTest
got error:
Running "qunit:ThriftJS_TLS" (qunit) task
Testing https://localhost:8091/test-nojq.html >> There was an error with
headless chrome
{color:red}*Fatal error: Navigation Timeout Exceeded: 5000ms exceeded*{color}
!image-2021-06-18-11-55-17-743.png!
Modify the file：
./compile-tools/thrift/target/thrift-0.14.1/lib/js/node_modules/puppeteer/lib/FrameManager.js
line 62
this._defaultNavigationTimeout = timeout*100;
line 76
timeout = this._defaultNavigationTimeout*100
line 123
timeout = this._defaultNavigationTimeout*100
line 537
timeout = 36
can solve the timeout problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1445) c++ : select * from dev (300 sensors * 10100000 points ) got Segmentation fault
刘珍 created IOTDB-1445:
-
Summary: c++ : select * from dev (300 sensors * 1010 points )
got Segmentation fault
Key: IOTDB-1445
URL: https://issues.apache.org/jira/browse/IOTDB-1445
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Others
Affects Versions: 0.12.0
Reporter: 刘珍
Attachments: image-2021-06-18-15-29-44-915.png
master 0616 / 699f866fb73d81c6d35ad6b401ceceb2499decbf
Author: J.J. Liu
Fix Cpp example not release query dataset bug (#3419)
benchmark generate test data：
INSERT_MODE=session
IS_CLIENT_BIND=true
CLIENT_NUMBER=20
GROUP_NUMBER=20
DEVICE_NUMBER=20
SENSOR_NUMBER=300
IS_SENSOR_TS_ALIGNMENT=true
BATCH_SIZE=10
LOOP=101
OPERATION_PROPORTION=1:0:0:0:0:0:0:0:0:0:0
IS_OVERFLOW=false
SessionExample.cpp :
void query({color:red}string dev{color}) {
unique_ptr dataSet =
session->executeQueryStatement({color:red}"select * from "+dev{color});
cout << "timestamp" << " ";
for (string name : dataSet->getColumnNames()) {
cout << name << " ";
}
cout << endl;
dataSet->setBatchSize(1024);
while (dataSet->hasNext())
{
cout << dataSet->next()->toString();
}
dataSet->closeOperationHandle();
}
int main() {
session = new Session("127.0.0.1", 6667, "root", "root");
session->open(false);
query("root.group_0.d_0");
query("root.group_1.d_1");
query("root.group_10.d_10");
query("root.group_11.d_11");
query("root.group_12.d_12");
query("root.group_13.d_13");
query("root.group_14.d_14");
query("root.group_15.d_15");
query("root.group_16.d_16");
query("root.group_17.d_17");
query("root.group_18.d_18");
query("root.group_19.d_19");
query("root.group_2.d_2");
query("root.group_3.d_3");
query("root.group_4.d_4");
query("root.group_5.d_5");
query("root.group_6.d_6");
query("root.group_7.d_7");
query("root.group_8.d_8");
query("root.group_9.d_9");
session->close();
return 0;
}
compile :
mvn package -P compile-cpp -pl example/client-cpp-example -am -DskipTest
run test ：
./SessionExample
{color:red}* Segmentation fault*{color}
!image-2021-06-18-15-29-44-915.png|thumbnail!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1434) cluster_scalability：Stop 1 node in the 2-node cluster，create timeseires successfully
刘珍 created IOTDB-1434: - Summary: cluster_scalability：Stop 1 node in the 2-node cluster，create timeseires successfully Key: IOTDB-1434 URL: https://issues.apache.org/jira/browse/IOTDB-1434 Project: Apache IoTDB Issue Type: Bug Components: Cluster Affects Versions: 0.12.0 Reporter: 刘珍 Attachments: image-2021-06-11-12-56-00-425.png cluster info : https://github.com/apache/iotdb/pull/3191 commit f1e98e4bb77f7b5f09149d396e8eee8463bd2fc5 Author: lta Date: Thu Jun 10 00:52:26 2021 +0800 iotdb-cluster.properties： seed_nodes=192.168.130.21:9003,192.168.130.13:9005 default_replica_num=1 node-21 execute : nohup ./sbin/start-node.sh > node21.out & node-13 execute: nohup ./sbin/start-node.sh > node13.out & node-21 cli execute: CREATE TIMESERIES root.ln.wf01.wt01.status WITH DATATYPE=BOOLEAN, ENCODING=PLAIN --successfully. node-13 execute: ./sbin/stop-server.sh [iotdb@fit21 node21]$ ./sbin/nodetool.sh status NodeStatus 192.168.130.21:9003:40010:6667->on 192.168.130.13:9005:40010:6667-> off node-21 cli execute: CREATE TIMESERIES root.ln.wf01.wt01.node21 WITH DATATYPE=BOOLEAN, ENCODING=PLAIN --successfully. I think,it should be failed，because more than half of the nodes in the cluster must be online to provide services. another question，node-21 cli： show timeseries; It costs 60.344s It costs too long。 !image-2021-06-11-12-56-00-425.png|thumbnail! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1438) cluster_scalability：add node，PathNotExistException
刘珍 created IOTDB-1438:
-
Summary: cluster_scalability：add node，PathNotExistException
Key: IOTDB-1438
URL: https://issues.apache.org/jira/browse/IOTDB-1438
Project: Apache IoTDB
Issue Type: Bug
Components: Cluster
Affects Versions: 0.12.0
Reporter: 刘珍
Attachments: image-2021-06-11-15-39-49-066.png
cluster version info :
https://github.com/apache/iotdb/pull/3191
commit f1e98e4bb77f7b5f09149d396e8eee8463bd2fc5
Author: lta
Date: Thu Jun 10 00:52:26 2021 +0800
node info ：
[iotdb@fit21 node21]$ ./sbin/nodetool.sh status
NodeStatus
192.168.130.13:9005:40010:6667->on
192.168.130.21:9003:40010:6667->on
benchmark-ip11 execute ingestion and queries on node-21
benchmark-ip13 execute ingestion and queries on node-13
ip11 execute :
add-node.sh
ip11 log print ( Service should be denied until metadata synchronization is
complete ）:
2021-06-11 15:31:23,637 [DataClientThread-16] WARN
o.a.i.d.metadata.MManager:2285 - meet error when check root.group_4.d_264.s_9
53, message: Path [root.group_4.d_264.s_953] does not exist
2021-06-11 15:31:23,637 [DataClientThread-20] INFO
o.a.i.d.e.v.SimpleFileVersionController:113 - Version file updated, previous:
/home/iotdb/liuzhen_test/cluster_scalability/node11/./sbin/../data/system/storage_groups/root.group_7/0/upgrade/Version-0,
curre nt:
/home/iotdb/liuzhen_test/cluster_scalability/node11/./sbin/../data/system/storage_groups/root.group_7/0/upgrade/Version-100
2021-06-11 15:31:23,638 [DataClientThread-13] ERROR o.a.t.ProcessFunction:47 -
Internal error processing pullTimeSeriesSchema
org.apache.thrift.TException:
org.apache.iotdb.db.exception.metadata.PathNotExistException: Path
[root.group_1.d_61.s_929] does n ot exist
at
org.apache.iotdb.cluster.server.service.DataSyncService.pullTimeSeriesSchema(DataSyncService.java:140)
at
org.apache.iotdb.cluster.server.DataClusterServer.pullTimeSeriesSchema(DataClusterServer.java:981)
at
org.apache.iotdb.cluster.rpc.thrift.TSDataService$Processor$pullTimeSeriesSchema.getResult(TSDataService.java:2376)
at
org.apache.iotdb.cluster.rpc.thrift.TSDataService$Processor$pullTimeSeriesSchema.getResult(TSDataService.java:2356)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.iotdb.db.exception.metadata.PathNotExistException: Path
{color:red}*[root.group_1.d_61.s_929] does not exist*{color}
at org.apache.iotdb.db.metadata.MTree.getNodeByPath(MTree.java:731)
at
org.apache.iotdb.db.metadata.MManager.getNodeByPath(MManager.java:1319)
at
org.apache.iotdb.db.metadata.MManager.collectTimeseriesSchema(MManager.java:1987)
at
org.apache.iotdb.cluster.query.LocalQueryExecutor.queryTimeSeriesSchema(LocalQueryExecutor.java:416)
at
org.apache.iotdb.cluster.server.service.DataSyncService.pullTimeSeriesSchema(DataSyncService.java:138)
... 9 common frames omitted
!image-2021-06-11-15-39-49-066.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1436) cluster_scalability：2-node cluster，benchmark execute ingestion ,got NPE
刘珍 created IOTDB-1436: - Summary: cluster_scalability：2-node cluster，benchmark execute ingestion ,got NPE Key: IOTDB-1436 URL: https://issues.apache.org/jira/browse/IOTDB-1436 Project: Apache IoTDB Issue Type: Bug Components: Cluster Affects Versions: 0.12.0 Reporter: 刘珍 Attachments: image-2021-06-11-14-34-55-839.png cluster version info : https://github.com/apache/iotdb/pull/3191 commit f1e98e4bb77f7b5f09149d396e8eee8463bd2fc5 Author: lta Date: Thu Jun 10 00:52:26 2021 +0800 iotdb-cluster.properties: seed_nodes=192.168.130.21:9003,192.168.130.13:9005 default_replica_num=1 start node-13 / node-21 [iotdb@fit21 node21]$ ./sbin/nodetool.sh ring Node Identifier Node -680018325 ->192.168.130.13:9005:40010:6667 (FOLLOWER) -679983576 ->192.168.130.21:9003:40010:6667 (LEADER) benchmark config.properties: HOST=192.168.130.21 PORT=6667 USE_CLUSTER_DB=false #Benchmark自身是否使用集群模式（多Benchmark） USE_CLUSTER=true #当使用集群模式时起效，设定FIRST_INDEX后，device的起始为 FIRST_INDEX*DEVICE_NUMBER FIRST_INDEX=3 #IoTDB:jdbc,sessionByRecord,sessionByRecords,sessionByTabletjdbc,session INSERT_MODE=sessionByTablet #客户端和设备是否绑定，若为false则客户端数可以大于设备数 IS_CLIENT_BIND=true #客户端并发数，若客户端和设备绑定，则必须小于等于设备数 CLIENT_NUMBER=10 #存储组数，必须小于等于设备数 GROUP_NUMBER=10 #存储组前缀，如果GROUP_NUMBER=3，则默认生成3个如下存储组：root.group_0、root.group_1、root.group_2 GROUP_NAME_PREFIX=group_ #总设备数 DEVICE_NUMBER=20 #每个设备的传感器数，总时间序列条数=DEVICE_NUMBER*SENSOR_NUMBER SENSOR_NUMBER=1000 #各sensor时间戳是否对齐 IS_SENSOR_TS_ALIGNMENT=true #批写入数据行数，每行是某个设备所有传感器在某一时间戳的数据，每个batch写入数据点数=SENSOR_NUMBER*BATCH_SIZE BATCH_SIZE=10 #Total number of operations that each client process LOOP=8 node-21 cli execute select: select count(s_1) from root.group_0.d_60 ; select count(s_1) from root.group_0.d_70 ; select count(s_1) from root.group_1.d_61 ; select count(s_1) from root.group_1.d_71 ; select count(s_1) from root.group_2.d_62 ; select count(s_1) from root.group_2.d_72 ; select count(s_1) from root.group_3.d_63 ; select count(s_1) from root.group_3.d_73 ; select count(s_1) from root.group_4.d_64 ; select count(s_1) from root.group_4.d_74 ; select count(s_1) from root.group_5.d_65 ; select count(s_1) from root.group_5.d_75 ; select count(s_1) from root.group_6.d_66 ; select count(s_1) from root.group_6.d_76 ; select count(s_1) from root.group_7.d_67 ; select count(s_1) from root.group_7.d_77 ; select count(s_1) from root.group_8.d_68 ; select count(s_1) from root.group_8.d_78 ; select count(s_1) from root.group_9.d_69 ; select count(s_1) from root.group_9.d_79 ; The recorders number of the timeseries in group_0/group_1/group_3/group_4/group_6/group_7/group_9 is 10 The recorders number of the timeseries in group_2/group_5/group_8 is as expected. benchmark got the exception: 2021-06-11 14:18:56,096 ERROR cn.edu.tsinghua.iotdb.benchmark.tsdb.DBWrapper:82 - Failed to insert one batch because unexpected exception: java.lang.NullPointerException: null Run benchmark on rel/0.12 (server) doesn't have this problem. !image-2021-06-11-14-34-55-839.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1369) 'merge' command cannot execute compaction task
[
https://issues.apache.org/jira/browse/IOTDB-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342220#comment-17342220
]
刘珍 commented on IOTDB-1369:
---
PR 3152 已验证，通过。
> 'merge' command cannot execute compaction task
> --
>
> Key: IOTDB-1369
> URL: https://issues.apache.org/jira/browse/IOTDB-1369
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Compaction
>Reporter: 张凌哲
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2021-05-10-14-06-39-750.png
>
>
> 1. Set IoTDB params like below:
> {code:java}
> enableMemControl: false
> memtableSizeThreshold: 1*1024*1024L{code}
> 2. Use SessionExample to write data util there are too much TsFile that
> cannot be compacted immediately like figure-1.
> !image-2021-05-10-14-06-39-750.png!
> 3. open cli and use `merge` command to execute compaction task.
>
> Problem: nothing happens after `merge` command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1313) import-csv can not indicate timestamp format，this causes millisecond is zero
[
https://issues.apache.org/jira/browse/IOTDB-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341195#comment-17341195
]
刘珍 commented on IOTDB-1313:
---
已解决
> import-csv can not indicate timestamp format，this causes millisecond is zero
>
>
> Key: IOTDB-1313
> URL: https://issues.apache.org/jira/browse/IOTDB-1313
> Project: Apache IoTDB
> Issue Type: Bug
>Reporter: 刘珍
>Priority: Minor
> Labels: pull-request-available
> Attachments: image-2021-04-19-16-58-15-628.png
>
>
> release 0.12.0
> cli构造数据:
> 构造数据：
> CREATE TIMESERIES [root.db1.tab1.id|http://root.db1.tab1.id/] WITH
> DATATYPE=INT32, ENCODING=PLAIN
> CREATE TIMESERIES [root.db1.tab1.name|http://root.db1.tab1.name/] WITH
> DATATYPE=text, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean, ENCODING=PLAIN
>
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),1,'lily',25,'usa',5678.34,7.77,false);
>
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),0,'lily0',25,'usa',5678.34,7.77,false);
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),1,'lily1',25,'usa',5678.34,7.77,false);
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),2,'lily2',25,'usa',5678.34,7.77,false);
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),3,'lily3',25,'usa',5678.34,7.77,false);
>
> 先export：
> select文件的内容：select * from root.db1.*
>
> ./export-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -tf
> {color:#FF}-MM-dd\'T\'HH:mm:ss.SSS{color} -td ./ -f dump_ts2.csv -s
> select
> 导出文件指定tf包含毫秒。导出结果：
> Time,root.db1.tab1.country,root.db1.tab1.other,root.db1.tab1.student,root.db1.tab1.name,root.db1.tab1.id,root.db1.tab1.salary,root.db1.tab1.age
> 2021-04-19T16:28:49{color:#FF}.810{color},usa,7.77,false,lily,1.0,5678.34,25.0
> 2021-04-19T16:28:49.818,usa,7.77,false,lily0,0.0,5678.34,25.0
> 2021-04-19T16:28:49.824,usa,7.77,false,lily1,1.0,5678.34,25.0
> 2021-04-19T16:28:49.828,usa,7.77,false,lily2,2.0,5678.34,25.0
> 2021-04-19T16:28:49.833,usa,7.77,false,lily3,3.0,5678.34,25.0
>
> cli删除数据：
> delete from root.db1.*;
> import导入数据：
> ./import-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -f ./dump_ts2.csv0.csv
> cli查询：
> select * from root.db1.*; --毫秒被截断置为0 ，import-csv不支持指定时间戳格式。
> !image-2021-04-19-16-58-15-628.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1315) export-csv.sh -tf yyyy-MM-dd\'T\'HH:mm:ss.SSSZ error： is not supported
[
https://issues.apache.org/jira/browse/IOTDB-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341242#comment-17341242
]
刘珍 commented on IOTDB-1315:
---
commit e9ada637017068ad9adb2e956f07288b1d44f60b
Author: Haonan
Date: Sat May 8 15:19:54 2021 +0800
[IOTDB-1232][IOTDB-1313] Fix lossing time precision when import csv with
unsupported timestamp format (#3142)
已解决。
> export-csv.sh -tf -MM-dd\'T\'HH:mm:ss.SSSZ error： is not supported
>
>
> Key: IOTDB-1315
> URL: https://issues.apache.org/jira/browse/IOTDB-1315
> Project: Apache IoTDB
> Issue Type: Bug
>Reporter: 刘珍
>Priority: Minor
> Labels: pull-request-available
> Attachments: image-2021-04-19-17-33-31-547.png,
> image-2021-04-19-17-34-40-690.png, image-2021-04-19-17-36-01-620.png
>
>
> release 0.12.0
> cli execute ：
> CREATE TIMESERIES [root.db1.tab1.id|http://root.db1.tab1.id/] WITH
> DATATYPE=INT32, ENCODING=PLAIN
> CREATE TIMESERIES [root.db1.tab1.name|http://root.db1.tab1.name/] WITH
> DATATYPE=text, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean, ENCODING=PLAIN
>
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),1,'lily',25,'usa',5678.34,7.77,false);
>
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),0,'lily0',25,'usa',5678.34,7.77,false);
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),1,'lily1',25,'usa',5678.34,7.77,false);
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),2,'lily2',25,'usa',5678.34,7.77,false);
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),3,'lily3',25,'usa',5678.34,7.77,false);
>
> select file ：
> select * from root.db1.*
> execute export indicate ts format ：
> ./export-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -tf
> {color:#FF}-MM-dd\'T\'HH:mm:ss.SSSZ{color} -td ./ -f dump_ts4 -s
> select
> --
> Starting IoTDB Client Export Script
> --
> Input time format -MM-dd'T'HH:mm:ss.SSSZ {color:#FF}is not
> supported{color}, please input like -MM-dd\ HH:mm:ss.SSS or
> -MM-dd'T'HH:mm:ss.SSS
> SimpleDateFormat中支持了，但是
> !image-2021-04-19-17-33-31-547.png!
>
> 这个里面没有加：
> !image-2021-04-19-17-36-01-620.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1330) After loading the TsFile file，reported an error In a clean server
[ https://issues.apache.org/jira/browse/IOTDB-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341258#comment-17341258 ] 刘珍 commented on IOTDB-1330: --- commit 8a500fe8875487091b5a1ccbba2bf7334ba8e2ba Author: Haonan Date: Fri May 7 11:40:17 2021 +0800 [To rel/0.12][IOTDB-1286] fix 4 C++ mem-leak points (#2976) (#3137) Co-authored-by: Jamber Co-authored-by: haiyi.zb 已解决。 > After loading the TsFile file，reported an error In a clean server > -- > > Key: IOTDB-1330 > URL: https://issues.apache.org/jira/browse/IOTDB-1330 > Project: Apache IoTDB > Issue Type: Bug > Components: Server >Affects Versions: 0.12.0 >Reporter: xiaozhihong >Assignee: Houliang Qi >Priority: Major > Labels: pull-request-available > > step 1： > No partition,write data by benchmark, and enter cli, then query data, > finally flush. > step 2: > Backup the generated TsFile file to new route > step 3: > Start a clean server, open the partition > step4: > Enter cli, load the TsFile > Actually，load failed > load "/home/xzh/0.12.0/load_TsFile/1619502355580-1-0-0.tsfile" true > Msg: 411: Cannot load file > /home/xzh/0.12.0/load_TsFile/1619502355580-1-0-0.tsfile because null > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1325) Count natural month query data results report stack overflow
[ https://issues.apache.org/jira/browse/IOTDB-1325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341213#comment-17341213 ] 刘珍 commented on IOTDB-1325: --- commit 8a500fe8875487091b5a1ccbba2bf7334ba8e2ba Author: Haonan Date: Fri May 7 11:40:17 2021 +0800 [To rel/0.12][IOTDB-1286] fix 4 C++ mem-leak points (#2976) (#3137) Co-authored-by: Jamber Co-authored-by: haiyi.zb 已解决。 > Count natural month query data results report stack overflow > > > Key: IOTDB-1325 > URL: https://issues.apache.org/jira/browse/IOTDB-1325 > Project: Apache IoTDB > Issue Type: Bug > Components: Server >Affects Versions: 0.12.0 > Environment: 192.168.130.11 >Reporter: xiaozhihong >Priority: Major > Labels: pull-request-available > Fix For: 0.12.1 > > > Steps: > > 1. insert into root.sg.d1(time,s1) values(152242560, 1) > 2. select count(*) from root.sg.d1 group by ((2018-01-31, 2018-03-31],1mo) > > log_error.log: > 2021-04-23 14:01:50,005 [pool-8-IoTDB-RPC-Client-8] ERROR > o.a.i.d.c.IoTDBDefaultThreadExceptionHandler:31 - Exception in thread > pool-8-IoTDB-RPC-Cl > ient-8-68 > java.lang.StackOverflowError: null > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.getNextIntervalAndSlidingStep(GroupByMonthFilter.java:166) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:73) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.apache.iotdb.tsfile.read.filter.GroupByMonthFilter.satisfy(GroupByMonthFilter.java:74) > at > org.
[jira] [Commented] (IOTDB-1316) A sensor point value is invalid and this row can be imported successfully，but the following rows in this file are not executed
[
https://issues.apache.org/jira/browse/IOTDB-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17341243#comment-17341243
]
刘珍 commented on IOTDB-1316:
---
修正一下2个csv文件的内容：
文件1：
Time,root.db1.tab1.country,root.db1.tab1.other,root.db1.tab1.student,root.db1.tab1.name,root.db1.tab1.id,root.db1.tab1.salary,root.db1.tab1.age
2021-05-08 14:04:29.001,usa,7.77,false,lily,11,5678.34,25
2021-05-08 14:04:29.002,usa,china,false,lily0,12,5678.34,35
2021-05-08 14:04:29.003,usa,7.77,false,lily1,13,5678.34,45
2021-05-08 14:04:29.004,usa,7.77,false,lily2,24,5678.34,55
2021-05-08 14:04:29.505,usa,7.77,false,lily3,35,5678.34,65
文件2：
Time,root.db1.tab1.country,root.db1.tab1.other,root.db1.tab1.student,root.db1.tab1.name,root.db1.tab1.id,root.db1.tab1.salary,root.db1.tab1.age
2021-05-08 14:14:29.401,usa,7.77,false,lily,1,5678.34,25
2021-05-08 14:14:29.502,usa,7.77,false,lily0,2,5678.34,25
2021-05-08 14:14:29.603,usa,7.77,false,lily1,3,5678.34,25
2021-05-08 14:14:29.708,usa,7.77,false,lily2,4,5678.34,25
2021-05-08 14:14:29.908,usa,7.77,false,lily3,5,5678.34,25
> A sensor point value is invalid and this row can be imported successfully，but
> the following rows in this file are not executed
> --
>
> Key: IOTDB-1316
> URL: https://issues.apache.org/jira/browse/IOTDB-1316
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 0.12.0
>Reporter: 刘珍
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2021-04-19-17-50-27-843.png,
> image-2021-05-06-21-03-07-103.png
>
>
> release 0.12.0
> A sensor point value is invalid and this row can be imported successfully(
> the sensor point is null)，but the following rows in this file are not
> executed。
> cli execute :
> {color:#172b4d}CREATE TIMESERIES
> {color}[{color:#0052cc}root.db1.tab1.id{color}|http://root.db1.tab1.id/]{color:#172b4d}
> WITH DATATYPE=INT32, ENCODING=PLAIN{color}
> {color:#172b4d}CREATE TIMESERIES
> {color}[{color:#0052cc}root.db1.tab1.name{color}|http://root.db1.tab1.name/]{color:#172b4d}
> WITH DATATYPE=text, ENCODING=PLAIN{color}
> {color:#172b4d}CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32,
> ENCODING=PLAIN{color}
> {color:#172b4d}CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text,
> ENCODING=PLAIN{color}
> {color:#172b4d}CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float,
> ENCODING=PLAIN{color}
> {color:#172b4d}CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double,
> ENCODING=PLAIN{color}
> {color:#172b4d}CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean,
> ENCODING=PLAIN{color}
> {color:#172b4d} {color}
> 2 import files locate in csv_file directory :
> *cat csv_file/dump_ts3.csv :*
> Time,root.db1.tab1.country,root.db1.tab1.other,root.db1.tab1.student,root.db1.tab1.name,root.db1.tab1.id,root.db1.tab1.salary,root.db1.tab1.age
> 2021-04-19T16:28:19,usa,china,false,丽丽,1.0,5678.34,25.0
> 2021-04-19T16:28:29,usa,7.77,false,支持,0.0,5678.34,25.0
> 2021-04-19T16:28:39,usa,7.77,false,lily,1.0,5678.34,25.0
> 2021-04-19T16:28:49,usa,7.77,false,lily2,2.0,5678.34,25.0
> 2021-04-19T16:28:59,usa,7.77,false,lily3,3.0,5678.34,25.0
>
> *cat csv_file/dump_ts4.csv :*
> Time,root.db1.tab1.country,root.db1.tab1.other,root.db1.tab1.student,root.db1.tab1.name,root.db1.tab1.id,root.db1.tab1.salary,root.db1.tab1.age
> 2021-04-19T16:29:19,usa,7.77,false,lily,1.0,5678.34,25.0
> 2021-04-19T16:29:29,usa,7.77,false,lily0,0.0,5678.34,25.0
> 2021-04-19T16:29:39,usa,7.77,false,lily1,1.0,5678.34,25.0
> 2021-04-19T16:29:49,usa,7.77,false,lily2,2.0,5678.34,25.0
> 2021-04-19T16:29:59,usa,7.77,false,lily3,3.0,5678.34,25.0
>
> import SQL:
> ./import-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -f ./csv_file
> --
> Starting IoTDB Client Import Script
> --
> Start to import data from: dump_ts3.csv
> Import from: dump_ts3.csv 0% │ │ 0/7 (0:00:00 / ?) Importing...
> Meet error when insert csv because
> org.apache.iotdb.db.exception.StorageEngineException: failed to insert
> measurements [other] {color:#FF}caused by For input string:
> "china";{color}
> Start to import data from: dump_ts4.csv
> Import from: dump_ts4.csv 0% │ │ 0/7 (0:00:00 / ?) Importing...
> Import from: dump_ts4.csv 100%
> │█████│ 7/7 (0:00:00 /
> 0:00:00) Importing...
>
> cli:
> select * from root.db1.*;
> !image-2021-04-19-17-50-27-843.png!
> The last 4 rows in dump_ts3.csv are not imported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1390) Unseq compaction loss data in seq file
张凌哲 created IOTDB-1390:
--
Summary: Unseq compaction loss data in seq file
Key: IOTDB-1390
URL: https://issues.apache.org/jira/browse/IOTDB-1390
Project: Apache IoTDB
Issue Type: Bug
Components: Compaction
Reporter: 张凌哲
Fix For: master branch, 0.11.4, 0.12.1
set compaction_strategy = LEVEL_COMPACTION
use the `data` to recover the IoTDB. After Recovery, it will merge the unseq
data automatically. After unseq compaction, the data of some sensor in seq file
loss.
use the following SQL to check data status before and after unseq compaction.
{code:java}
select Channel96 from root.*.J053102.T034.V1 where time >= 2021-05-18 22:32:27
and time <= 2021-05-18 22:32:37;
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1274) ./sbin/start-cli.sh -e 'select last * from root.*' Parser error : Msg: 401
[
https://issues.apache.org/jira/browse/IOTDB-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352364#comment-17352364
]
刘珍 commented on IOTDB-1274:
---
./sbin/start-cli.sh -p 6677 -e 'select last* from root'
*和前面的单词连着。可以执行。
> ./sbin/start-cli.sh -e 'select last * from root.*' Parser error : Msg: 401
>
>
> Key: IOTDB-1274
> URL: https://issues.apache.org/jira/browse/IOTDB-1274
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/CLI
>Reporter: 刘珍
>Priority: Minor
>
> 0.11.3 9e371454b05f9a0e24fabb2c84f7ce690f14a882
> {color:#FF}start-cli.sh -e SQL contains * parser error{color}
> {color:#FF}Msg: 401: line 1:18 mismatched input 'conf' expecting \{FROM,
> ',', '.'}{color}
>
> set storage group root.db1;
> CREATE TIMESERIES root.db1.tab1.id WITH DATATYPE=INT32, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.name WITH DATATYPE=text, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean, ENCODING=PLAIN
>
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),1,'lily',25,'usa',5678.34,7.77,false);
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),2,'lily2',25,'usa',5678.34,7.77,false);
>
> ./sbin/start-cli.sh{color:#FF} -e{color} 'select last * from root.*'
> Msg: 401: line 1:18 mismatched input 'conf' expecting \{FROM, ',', '.'}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1274) ./sbin/start-cli.sh -e 'select last * from root.*' Parser error : Msg: 401
[
https://issues.apache.org/jira/browse/IOTDB-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17358312#comment-17358312
]
刘珍 commented on IOTDB-1274:
---
已解决。
> ./sbin/start-cli.sh -e 'select last * from root.*' Parser error : Msg: 401
>
>
> Key: IOTDB-1274
> URL: https://issues.apache.org/jira/browse/IOTDB-1274
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/CLI
>Reporter: 刘珍
>Priority: Minor
>
> 0.11.3 9e371454b05f9a0e24fabb2c84f7ce690f14a882
> {color:#FF}start-cli.sh -e SQL contains * parser error{color}
> {color:#FF}Msg: 401: line 1:18 mismatched input 'conf' expecting \{FROM,
> ',', '.'}{color}
>
> set storage group to root.db1;
> CREATE TIMESERIES root.db1.tab1.id WITH DATATYPE=INT32, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.name WITH DATATYPE=text, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double, ENCODING=PLAIN
> CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean, ENCODING=PLAIN
>
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),1,'lily',25,'usa',5678.34,7.77,false);
> insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
> values(now(),2,'lily2',25,'usa',5678.34,7.77,false);
>
> ./sbin/start-cli.sh{color:#FF} -e{color} 'select last * from root.*'
> Msg: 401: line 1:18 mismatched input 'conf' expecting \{FROM, ',', '.'}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1401) Tablet's rowsize = 0 ,insertTablets throws an exception ,gives an unfriendly error message
[
https://issues.apache.org/jira/browse/IOTDB-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17358330#comment-17358330
]
刘珍 commented on IOTDB-1401:
---
已解决。
> Tablet's rowsize = 0 ,insertTablets throws an exception ,gives an unfriendly
> error message
> --
>
> Key: IOTDB-1401
> URL: https://issues.apache.org/jira/browse/IOTDB-1401
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Server
>Affects Versions: 0.12.0
>Reporter: 刘珍
>Priority: Minor
> Attachments: image-2021-05-27-16-05-45-882.png
>
>
> [rel/0.12] 05/18 99822c7feb7797f33b0e740b0f3ea38803d11d17
> iotdb log :
> !image-2021-05-27-16-05-45-882.png|thumbnail!
> org.apache.iotdb.db.exception.BatchProcessException: {color:red}*Batch
> process failed:[]*{color}
> at
> org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.insertTablet(StorageGroupProcessor.java:858)
> test case：
> import org.apache.iotdb.rpc.IoTDBConnectionException;
> import org.apache.iotdb.rpc.StatementExecutionException;
> import org.apache.iotdb.rpc.TSStatusCode;
> import org.apache.iotdb.session.Session;
> import org.apache.iotdb.session.SessionDataSet;
> import org.apache.iotdb.session.SessionDataSet.DataIterator;
> import org.apache.iotdb.tsfile.file.metadata.enums.CompressionType;
> import org.apache.iotdb.tsfile.file.metadata.enums.TSDataType;
> import org.apache.iotdb.tsfile.file.metadata.enums.TSEncoding;
> import org.apache.iotdb.tsfile.write.record.Tablet;
> import org.apache.iotdb.tsfile.write.schema.MeasurementSchema;
> import java.util.ArrayList;
> import java.util.HashMap;
> import java.util.List;
> import java.util.Map;
> import java.util.Random;
> @SuppressWarnings("squid:S106")
> public class SessionExample {
> private static Session session;
> private static Session sessionEnableRedirect;
> private static final String ROOT_SG1_D1_S1 = "root.sg1.d1.s1";
> private static final String ROOT_SG1_D1_S2 = "root.sg1.d1.s2";
> private static final String ROOT_SG1_D1_S3 = "root.sg1.d1.s3";
> private static final String ROOT_SG1_D1_S4 = "root.sg1.d1.s4";
> private static final String ROOT_SG1_D1_S5 = "root.sg1.d1.s5";
> private static final String ROOT_SG1_D1 = "root.sg1.d1";
> private static final String LOCAL_HOST = "127.0.0.1";
> public static void main(String[] args)
> throws IoTDBConnectionException, StatementExecutionException {
> session = new Session(LOCAL_HOST, 6667, "root", "root");
> session.open(false);
> // set session fetchSize
> session.setFetchSize(1);
> try {
> session.setStorageGroup("root.sg1");
> } catch (StatementExecutionException e) {
> if (e.getStatusCode() !=
> TSStatusCode.PATH_ALREADY_EXIST_ERROR.getStatusCode()) {
> throw e;
> }
> }
> createTimeseries();
> createMultiTimeseries();
> insertTablets();
> session.close();
> }
> private static void createTimeseries()
> throws IoTDBConnectionException, StatementExecutionException {
> if (!session.checkTimeseriesExists(ROOT_SG1_D1_S1)) {
> session.createTimeseries(
> ROOT_SG1_D1_S1, TSDataType.INT64, TSEncoding.RLE,
> CompressionType.SNAPPY);
> }
> if (!session.checkTimeseriesExists(ROOT_SG1_D1_S2)) {
> session.createTimeseries(
> ROOT_SG1_D1_S2, TSDataType.INT64, TSEncoding.RLE,
> CompressionType.SNAPPY);
> }
> if (!session.checkTimeseriesExists(ROOT_SG1_D1_S3)) {
> session.createTimeseries(
> ROOT_SG1_D1_S3, TSDataType.INT64, TSEncoding.RLE,
> CompressionType.SNAPPY);
> }
> // create timeseries with tags and attributes
> if (!session.checkTimeseriesExists(ROOT_SG1_D1_S4)) {
> Map tags = new HashMap<>();
> tags.put("tag1", "v1");
> Map attributes = new HashMap<>();
> tags.put("description", "v1");
> session.createTimeseries(
> ROOT_SG1_D1_S4,
> TSDataType.INT64,
> TSEncoding.RLE,
> CompressionType.SNAPPY,
> null,
> tags,
> attributes,
> "temperature");
> }
> // create timeseries with SDT property, SDT will take place when flushing
> if (!session.checkTimeseriesExists(ROOT_SG1_D1_S5)) {
> // COMPDEV is required
&
[jira] [Created] (IOTDB-1401) Tablet's rowsize = 0 ,insertTablets throws an exception ,gives an unfriendly error message
刘珍 created IOTDB-1401:
-
Summary: Tablet's rowsize = 0 ,insertTablets throws an exception
,gives an unfriendly error message
Key: IOTDB-1401
URL: https://issues.apache.org/jira/browse/IOTDB-1401
Project: Apache IoTDB
Issue Type: Bug
Components: Server
Affects Versions: 0.12.0
Reporter: 刘珍
Attachments: image-2021-05-27-16-05-45-882.png
[rel/0.12] 05/18 99822c7feb7797f33b0e740b0f3ea38803d11d17
iotdb log :
!image-2021-05-27-16-05-45-882.png|thumbnail!
org.apache.iotdb.db.exception.BatchProcessException: {color:red}*Batch process
failed:[]*{color}
at
org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.insertTablet(StorageGroupProcessor.java:858)
test case：
import org.apache.iotdb.rpc.IoTDBConnectionException;
import org.apache.iotdb.rpc.StatementExecutionException;
import org.apache.iotdb.rpc.TSStatusCode;
import org.apache.iotdb.session.Session;
import org.apache.iotdb.session.SessionDataSet;
import org.apache.iotdb.session.SessionDataSet.DataIterator;
import org.apache.iotdb.tsfile.file.metadata.enums.CompressionType;
import org.apache.iotdb.tsfile.file.metadata.enums.TSDataType;
import org.apache.iotdb.tsfile.file.metadata.enums.TSEncoding;
import org.apache.iotdb.tsfile.write.record.Tablet;
import org.apache.iotdb.tsfile.write.schema.MeasurementSchema;
import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.Random;
@SuppressWarnings("squid:S106")
public class SessionExample {
private static Session session;
private static Session sessionEnableRedirect;
private static final String ROOT_SG1_D1_S1 = "root.sg1.d1.s1";
private static final String ROOT_SG1_D1_S2 = "root.sg1.d1.s2";
private static final String ROOT_SG1_D1_S3 = "root.sg1.d1.s3";
private static final String ROOT_SG1_D1_S4 = "root.sg1.d1.s4";
private static final String ROOT_SG1_D1_S5 = "root.sg1.d1.s5";
private static final String ROOT_SG1_D1 = "root.sg1.d1";
private static final String LOCAL_HOST = "127.0.0.1";
public static void main(String[] args)
throws IoTDBConnectionException, StatementExecutionException {
session = new Session(LOCAL_HOST, 6667, "root", "root");
session.open(false);
// set session fetchSize
session.setFetchSize(1);
try {
session.setStorageGroup("root.sg1");
} catch (StatementExecutionException e) {
if (e.getStatusCode() !=
TSStatusCode.PATH_ALREADY_EXIST_ERROR.getStatusCode()) {
throw e;
}
}
createTimeseries();
createMultiTimeseries();
insertTablets();
session.close();
}
private static void createTimeseries()
throws IoTDBConnectionException, StatementExecutionException {
if (!session.checkTimeseriesExists(ROOT_SG1_D1_S1)) {
session.createTimeseries(
ROOT_SG1_D1_S1, TSDataType.INT64, TSEncoding.RLE,
CompressionType.SNAPPY);
}
if (!session.checkTimeseriesExists(ROOT_SG1_D1_S2)) {
session.createTimeseries(
ROOT_SG1_D1_S2, TSDataType.INT64, TSEncoding.RLE,
CompressionType.SNAPPY);
}
if (!session.checkTimeseriesExists(ROOT_SG1_D1_S3)) {
session.createTimeseries(
ROOT_SG1_D1_S3, TSDataType.INT64, TSEncoding.RLE,
CompressionType.SNAPPY);
}
// create timeseries with tags and attributes
if (!session.checkTimeseriesExists(ROOT_SG1_D1_S4)) {
Map tags = new HashMap<>();
tags.put("tag1", "v1");
Map attributes = new HashMap<>();
tags.put("description", "v1");
session.createTimeseries(
ROOT_SG1_D1_S4,
TSDataType.INT64,
TSEncoding.RLE,
CompressionType.SNAPPY,
null,
tags,
attributes,
"temperature");
}
// create timeseries with SDT property, SDT will take place when flushing
if (!session.checkTimeseriesExists(ROOT_SG1_D1_S5)) {
// COMPDEV is required
// COMPMAXTIME and COMPMINTIME are optional and their unit is ms
Map props = new HashMap<>();
props.put("LOSS", "sdt");
props.put("COMPDEV", "0.01");
props.put("COMPMINTIME", "2");
props.put("COMPMAXTIME", "10");
session.createTimeseries(
ROOT_SG1_D1_S5,
TSDataType.INT64,
TSEncoding.RLE,
CompressionType.SNAPPY,
props,
null,
null,
null);
}
}
private static void createMultiTimeseries()
throws IoTDBConnectionException, StatementExecutionException {
if (!session.checkTimeseriesExists("root.sg1.d2.s1")
&& !session.checkTimeseriesExists(&
[jira] [Created] (IOTDB-1420) Compaction process conflicts with TTL process
张凌哲 created IOTDB-1420: -- Summary: Compaction process conflicts with TTL process Key: IOTDB-1420 URL: https://issues.apache.org/jira/browse/IOTDB-1420 Project: Apache IoTDB Issue Type: Bug Components: Compaction Reporter: 张凌哲 Fix For: 0.11.4, 0.12.1 The compaction process needs to get all readers of the files to be compacted and close all of them after this compaction finish. However, if one of the reader of the file cannot be get(it may be deleted by TTL process), the whole compaction will just throw out and the open reader cannot be closed. If the problem above continuously occurs. There will be too many file reader cannot be closed. And cause `too many opened files` error. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1473) Rel 0.12.1 cluster：insertTablets StatementExecutionException:400:null
刘珍 created IOTDB-1473: - Summary: Rel 0.12.1 cluster：insertTablets StatementExecutionException:400:null Key: IOTDB-1473 URL: https://issues.apache.org/jira/browse/IOTDB-1473 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.12.1 Reporter: 刘珍 Attachments: image-2021-07-08-11-27-45-793.png Release 0.12.1 cluster : 3 nodes ,2 replications : seed_nodes=192.168.130.13:9003,192.168.130.11:9001,192.168.130.14:9004 default_replica_num=2 1. Start node-13,node-11,node-14 2. compile SessionExample.java ./example/session/src/main/java/org/apache/iotdb/SessionExample.java 3. Run SessionExample !image-2021-07-08-11-27-45-793.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1474) Suggestion : Don't “Auto Close” the dataset while there is no more data
刘珍 created IOTDB-1474: - Summary: Suggestion : Don't “Auto Close” the dataset while there is no more data Key: IOTDB-1474 URL: https://issues.apache.org/jira/browse/IOTDB-1474 Project: Apache IoTDB Issue Type: Bug Components: JDBC Affects Versions: 0.12.1 Reporter: 刘珍 Release note 0.12.1 ： [IOTDB-1380] Automatically close the dataset while there is no more data According to the JDBC interface standard, the cursor in the ResultSet can be rolled forward. 参照JDBC接口标准，ResultSet中的游标可前滚，如果遍历1遍就关闭， 再次遍历，就得重新查询，而不能前滚。 建议不要这么实现。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1462) Fix cross space compaction recover failed because of virtualStorageGroup
张凌哲 created IOTDB-1462:
--
Summary: Fix cross space compaction recover failed because of
virtualStorageGroup
Key: IOTDB-1462
URL: https://issues.apache.org/jira/browse/IOTDB-1462
Project: Apache IoTDB
Issue Type: Bug
Reporter: 张凌哲
Currently, when we recover cross space compaction, We pass
${logicalStorageName}-${virtualStorageGroupId} to find its timeseries in
MManager which must be empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1457) ”No space left on device“ causes iotdb system mode is read-only，iotdb does not have to be restarted when the device has available space
刘珍 created IOTDB-1457: - Summary: ”No space left on device“ causes iotdb system mode is read-only，iotdb does not have to be restarted when the device has available space Key: IOTDB-1457 URL: https://issues.apache.org/jira/browse/IOTDB-1457 Project: Apache IoTDB Issue Type: Bug Components: Server Affects Versions: 0.11.3, 0.12.0 Reporter: 刘珍 ”No space left on device“ causes iotdb system mode is read-only，iotdb does not have to be restarted when the device has available space. 磁盘空间不足导致的数据库read-only，建议：磁盘有可用空间时，数据库可以正常服务，不需要重启。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1483) Metadata template : LevelCompactionTsFileManagement NPE
刘珍 created IOTDB-1483:
-
Summary: Metadata template : LevelCompactionTsFileManagement NPE
Key: IOTDB-1483
URL: https://issues.apache.org/jira/browse/IOTDB-1483
Project: Apache IoTDB
Issue Type: Bug
Components: Schema Manager
Reporter: 刘珍
Attachments: SessionExample.java, config.properties,
image-2021-07-12-13-53-28-470.png
master/0708 18ae729e2792c709b7054cb0de25f4d331d7558e
MAX_HEAP_SIZE="128G"
Use the device template when merging {color:red}LevelCompactionTsFileManagement
get NPE.{color}
2021-07-11 00:31:47,695 [pool-4-IoTDB-Compaction-3] ERROR
o.a.i.d.e.c.l.LevelCompactionTsFileManagement:738 - Error occurred in
Compaction Merge thread
java.lang.NullPointerException: null
at
org.apache.iotdb.db.metadata.MManager.getSeriesSchema(MManager.java:1112)
at
org.apache.iotdb.db.engine.compaction.utils.CompactionUtils.writeByDeserializePageMerge(CompactionUtils.java:204)
at
org.apache.iotdb.db.engine.compaction.utils.CompactionUtils.merge(CompactionUtils.java:406)
at
org.apache.iotdb.db.engine.compaction.level.LevelCompactionTsFileManagement.merge(LevelCompactionTsFileManagement.java:685)
at
org.apache.iotdb.db.engine.compaction.level.LevelCompactionTsFileManagement.merge(LevelCompactionTsFileManagement.java:598)
at
org.apache.iotdb.db.engine.compaction.TsFileManagement$CompactionMergeTask.call(TsFileManagement.java:173)
at
org.apache.iotdb.db.engine.compaction.TsFileManagement$CompactionMergeTask.call(TsFileManagement.java:160)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
!image-2021-07-12-13-53-28-470.png!
复现过程（可减少数据量复现，满足合并条件就可以）：
100 sg/100万device/30 sensor（template）
1. 执行SessionExample
2.运行benchmark
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1492) mLogParser.sh cannot parse the device template
刘珍 created IOTDB-1492: - Summary: mLogParser.sh cannot parse the device template Key: IOTDB-1492 URL: https://issues.apache.org/jira/browse/IOTDB-1492 Project: Apache IoTDB Issue Type: Bug Components: Tools/Others Affects Versions: master branch Reporter: 刘珍 master/0708 18ae729e2792c709b7054cb0de25f4d331d7558e 1. Use session create device template setSchemaTemplate 2. cli or benchmark write data that belongs to the template tools/mlog/mLogParser.sh -f data/system/schema/mlog.bin -o dev_temp_mlog.out There is only SG information in “dev_temp_mlog.out” mLogParser.sh cannot parse the device template -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1481) Modify the problem in the IoTDB v0.12 UserGuide
张洪胤 created IOTDB-1481: -- Summary: Modify the problem in the IoTDB v0.12 UserGuide Key: IOTDB-1481 URL: https://issues.apache.org/jira/browse/IOTDB-1481 Project: Apache IoTDB Issue Type: Improvement Components: Document Reporter: 张洪胤 Fix For: 0.12.0 In the process of reading the UserGuide, some format errors in the document ware found. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1468) Rel 0.12.1 cluster：function max_time(sensor) query result is incorrect
刘珍 created IOTDB-1468:
-
Summary: Rel 0.12.1 cluster：function max_time(sensor) query result
is incorrect
Key: IOTDB-1468
URL: https://issues.apache.org/jira/browse/IOTDB-1468
Project: Apache IoTDB
Issue Type: Bug
Components: Cluster
Affects Versions: 0.12.1
Reporter: 刘珍
Attachments: image-2021-07-06-17-28-15-709.png,
image-2021-07-06-17-31-11-330.png
version info
Release 0.12.1
nodes info :
node-13,node-14,node-11
iotdb-cluster.properties
seed_nodes=192.168.130.13:9003,192.168.130.11:9001,192.168.130.14:9004
default_replica_num=2
start node-13,node-14,node-11
iotdb benchmark connect node-13 :
INSERT_MODE=sessionByTablet
IS_CLIENT_BIND=true
CLIENT_NUMBER=50
GROUP_NUMBER=20
GROUP_NAME_PREFIX=group_
DEVICE_NUMBER=1000
SENSOR_NUMBER=1000
IS_SENSOR_TS_ALIGNMENT=true
BATCH_SIZE=10
LOOP=9000
{color:red}*IS_OVERFLOW=false*{color}
FIRST_INDEX=2
Run for 2 hours , {color:red}*stop testing*{color}：
node-13 start-cli.sh :
select max_time(s_1) from root.group_9.d_2989 ; // {color:red}*result is
incorrect *{color}
select count(s_1) from root.group_9.d_2989 where time>=1537430295000
!image-2021-07-06-17-31-11-330.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1461) Compaction conflicts with TTL
张凌哲 created IOTDB-1461: -- Summary: Compaction conflicts with TTL Key: IOTDB-1461 URL: https://issues.apache.org/jira/browse/IOTDB-1461 Project: Apache IoTDB Issue Type: Bug Reporter: 张凌哲 When enable compaction, some files out of TTL may be compacted firstly and then be deleted by the TTL process. This is normal. However, some files out of TTL cannot be deleted even if they are not in compaction. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1469) Cross space compaction loss data
张凌哲 created IOTDB-1469: -- Summary: Cross space compaction loss data Key: IOTDB-1469 URL: https://issues.apache.org/jira/browse/IOTDB-1469 Project: Apache IoTDB Issue Type: Bug Components: Compaction Reporter: 张凌哲 Fix For: 0.11.4, 0.12.1 Attachments: image-2021-07-06-17-53-45-812.png Some data lost after cross space compaction. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1328) Delete one row from a tsfile which produces mods file,but the current tsfile also produces mods file .
刘珍 created IOTDB-1328: - Summary: Delete one row from a tsfile which produces mods file,but the current tsfile also produces mods file . Key: IOTDB-1328 URL: https://issues.apache.org/jira/browse/IOTDB-1328 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.12.0 Reporter: 刘珍 Attachments: image-2021-04-26-17-33-34-541.png rel/0.12 git log: commit 7feb9189718a8d0dcd0a3b07821ab6f03019d244 Author: wangchao316 <66939405+wangchao...@users.noreply.github.com> Date: Thu Apr 22 18:16:48 2021 +0800 [To rel/0.12][IOTDB-1301] snappy compatible arm64 (#3047) 1. benchmark seq ingestion （weekly test）。 print-tsfile-sketch.sh 1619471569450-26-0-0.tsfile 获取任一tsfile中的sensor的时间范围 cli execute ，delete one row： select s_411 from root.group_0.d_10 where time= 154389030; delete from root.group_0.d_10.s_411 where time = 154389030 ; select s_411 from root.group_0.d_10 where time= 154389030; check tsfile list : current tsfile should not produce mods file. !image-2021-04-26-17-33-34-541.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1220) MQTT insert 10 rows ，elapsed time is 5s ，and the inserted row count is less than 10.
[
https://issues.apache.org/jira/browse/IOTDB-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17332989#comment-17332989
]
刘珍 commented on IOTDB-1220:
---
master
commit f585d02a3cbe217caaab41de43e22570f4b0db8f
Author: Haonan
Date: Tue Apr 27 13:35:29 2021 +0800
[IOTDB-1220] MQTT example may have timestamp precision issue (#3074)
Resolved。
> MQTT insert 10 rows ，elapsed time is 5s ，and the inserted row count is less
> than 10.
>
>
> Key: IOTDB-1220
> URL: https://issues.apache.org/jira/browse/IOTDB-1220
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Server
>Reporter: 刘珍
>Priority: Minor
> Labels: pull-request-available
>
> master branch.
> commit id :5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
>
> #
> ## Usage
> * Update configuration to enable MQTT service. (`enable_mqtt_service=true`
> in iotdb-engine.properties)
> * Launch the IoTDB server.
> * Setup storage group `SET STORAGE GROUP TO root.sg` and create time
> timeseries `CREATE TIMESERIES root.sg.d1.s1 WITH DATATYPE=DOUBLE,
> ENCODING=PLAIN`.
> * Run `org.apache.iotdb.mqtt.MQTTClient` to run the mqtt client and send
> events to server.
> cat ../../src/main/java/org/apache/iotdb/mqtt/MQTTClient.java
>
> {code:java}
> package org.apache.iotdb.mqtt;
> import org.fusesource.mqtt.client.BlockingConnection;
> import org.fusesource.mqtt.client.MQTT;
> import org.fusesource.mqtt.client.QoS;
> import java.util.Random;
> public class MQTTClient {
> public static void main(String[] args) throws Exception {
> MQTT mqtt = new MQTT();
> mqtt.setHost("127.0.0.1", 1883);
> mqtt.setUserName("root");
> mqtt.setPassword("root");
> BlockingConnection connection = mqtt.blockingConnection();
> connection.connect();
> Random random = new Random();
> for (int i = 0; i < 10; i++) {
> String payload =
> String.format(
> "{\n" + "\"device\":\"root.sg.d1\",\n" + "\"timestamp\":%d,\n"
> + "\"measurements\":[\"s1\"],\n" + "\"values\":[%f]\n" + "}",
>System.currentTimeMillis(), random.nextDouble());
> connection.publish("root.sg.d1.s1", payload.getBytes(),
> QoS.AT_LEAST_ONCE, false);
> }
> connection.disconnect();
> }
> }
> {code}
>
> run time java -classpath ".:" org/apache/iotdb/mqtt/MQTTClient
> 2 times,the elapsed time:
> real 0m5.573s
> user 0m0.352s
> sys 0m0.055s
> real 0m0.584s
> user 0m0.371s
> sys 0m0.039s
>
> IoTDB> select s1 from root.sg.d1;
> +--++
> |Time|root.sg.d1.s1|
> +--++
> |2021-03-12T11:52:50.687+08:00|0.338776|
> |2021-03-12T11:52:50.692+08:00|0.250776|
> |2021-03-12T11:52:50.694+08:00|0.575861|
> |2021-03-12T11:52:50.695+08:00|0.229369|
> |2021-03-12T11:52:50.696+08:00|0.149007|
> |2021-03-12T11:52:50.697+08:00|0.182348|
> |2021-03-12T11:52:50.698+08:00|0.334755|
> |2021-03-12T11:52:50.699+08:00|0.757181|
> |2021-03-12T11:53:02.649+08:00|0.618037|
> |2021-03-12T11:53:02.655+08:00|0.789077|
> |2021-03-12T11:53:02.656+08:00|0.797554|
> |2021-03-12T11:53:02.657+08:00|0.660189|
> |2021-03-12T11:53:02.658+08:00|0.70841|
> |2021-03-12T11:53:02.659+08:00|0.09|
> |2021-03-12T11:53:02.660+08:00|0.130961|
> +--++
> Total line number = 15
> It costs 0.014s
> the "Total line number" should be 20.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1293) There is data in iotdb modify parameter enable_partition=true ,restart iotdb ,the error message is not clear
[
https://issues.apache.org/jira/browse/IOTDB-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333005#comment-17333005
]
刘珍 commented on IOTDB-1293:
---
2021-04-27 15:36:33,550 [main] ERROR o.a.i.d.c.IoTDBConfigCheck:333 -
{color:#FF}Wrong enable_partition, please set as: false !{color}
{color:#FF}iotdb：{color}
commit 7ecccf50ae46ea0f62bfbfa37525797ad1efee0c
Author: Haonan
Date: Tue Apr 27 15:11:59 2021 +0800
[IOTDB-1293] Message of enable_partition cannot be modified after iotdb started
should be more clear (#3075)
> There is data in iotdb modify parameter enable_partition=true ,restart iotdb
> ,the error message is not clear
>
>
> Key: IOTDB-1293
> URL: https://issues.apache.org/jira/browse/IOTDB-1293
> Project: Apache IoTDB
> Issue Type: Bug
>Reporter: 刘珍
>Priority: Minor
> Labels: pull-request-available
>
> 0.11.3 9e371454b05f9a0e24fabb2c84f7ce690f14a882
> There is data in iotdb.
> modify enable_partition=true
> restart iotdb,the error message is not clear:
> 2021-04-06 10:47:49,407 [main] ERROR
> org.apache.iotdb.db.conf.IoTDBConfigCheck:306 - Wrong
> partition_interval,{color:#ff} please set as: 9223372036854775807 !{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1340) 使用DBeaver客户端用jdbc的方式连接IOTDB无法连接
刘华 created IOTDB-1340: - Summary: 使用DBeaver客户端用jdbc的方式连接IOTDB无法连接 Key: IOTDB-1340 URL: https://issues.apache.org/jira/browse/IOTDB-1340 Project: Apache IoTDB Issue Type: Wish Components: JDBC Reporter: 刘华 希望能提供可以供数据库管理工具以jdbc方式连接iotdb的jar包 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1239) Incorrect datetime value can be inserted into iotdb successfully.
[
https://issues.apache.org/jira/browse/IOTDB-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335184#comment-17335184
]
刘珍 commented on IOTDB-1239:
---
这个报错也有问题，和insert成功的表现不一致。
!image-2021-04-29-14-54-43-270.png!
> Incorrect datetime value can be inserted into iotdb successfully.
> -
>
> Key: IOTDB-1239
> URL: https://issues.apache.org/jira/browse/IOTDB-1239
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/CLI
>Reporter: 刘珍
>Priority: Minor
> Labels: pull-request-available
> Attachments: image-2021-04-29-14-54-43-270.png
>
>
> master branch.
> commit id 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7 .
>
> SET STORAGE GROUP TO root.sg
> CREATE TIMESERIES root.sg.d1.s2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
> insert into root.sg.d1(time,s2 ) values (15741792,8.76);
> IoTDB> select * from root.sg.d1;
> +---+-+
> | Time|root.sg.d1.s2|
> +---+-+
> |{color:#FF}+{color}51853-10-03T00:00:{color:#FF}.0{color}+08:00|
> 8.76|
> +---+-+
> {color:#FF}should be give an error :{color}
> {color:#FF}Incorrect datetime value {color}
> IoTDB> select * from root.sg.d1 where time=51853-10-03T00:00:.0+08:00
> Msg: 401: Error occurred while parsing SQL to physical plan: line 1:36
> extraneous input '51853-10-03T00:00:' expecting \{NOW, TRUE, FALSE, '-', '.',
> 'NaN', INT, EXPONENT, DATETIME, DOUBLE_QUOTE_STRING_LITERAL,
> SINGLE_QUOTE_STRING_LITERAL}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1212) select sin(not_exist) from root.sg1.d1; The error message is not right.
[
https://issues.apache.org/jira/browse/IOTDB-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335316#comment-17335316
]
刘珍 commented on IOTDB-1212:
---
通过。rel/0.12
git log
commit f74425589e2f7211d8bd318fb95607c602d8a923
Author: Zesong Sun
Date: Thu Apr 29 17:45:01 2021 +0800
Add TsFileSequenceReader getChunkMetadataList method return empty if path not
exists (#3111)
commit d979bfd3cc2c4fd78b1890b73c61e73599b43c5d
Author: Steve Yurong Su
Date: Thu Apr 29 17:39:35 2021 +0800
[To rel/0.12][IOTDB-1212] The given error message is not right when executing
`select sin(non_existence) from root.sg1.d1` (#3102)
!image-2021-04-29-18-00-30-051.png!
> select sin(not_exist) from root.sg1.d1; The error message is not right.
>
>
> Key: IOTDB-1212
> URL: https://issues.apache.org/jira/browse/IOTDB-1212
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/Java
>Reporter: 刘珍
>Priority: Minor
> Labels: pull-request-available
> Fix For: 0.12.1
>
> Attachments: image-2021-04-29-18-00-30-051.png
>
>
> master branch
> commit id : 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
>
> SET STORAGE GROUP TO root.sg1;
> CREATE TIMESERIES root.sg1.d1.s1 WITH DATATYPE=INT32, ENCODING=PLAIN;
> CREATE TIMESERIES root.sg1.d1.s2 WITH DATATYPE=INT32, ENCODING=PLAIN;
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (0, -1, 1);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (1, -2, 2);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (2, -3, 3);
> select sin(not_exist) from root.sg1.d1;
>
> Msg: 411: Error occurred in query process: Error occurred during executing
> UDTF#validate(UDFParameterValidator):
> {color:#FF}org.apache.iotdb.db.query.udf.api.exception.UDFInputSeriesNumberNotValidException:
> the number of the input series is not valid. expected: 1. actual: 0.{color}
> {color:#FF}The error message is not right.{color}
> {color:#ff0000}The actual is the input series does not exist.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1149) start-cli.sh -e 'select statement' > result.out have to Press ENTER and complete the output
刘珍 created IOTDB-1149: - Summary: start-cli.sh -e 'select statement' > result.out have to Press ENTER and complete the output Key: IOTDB-1149 URL: https://issues.apache.org/jira/browse/IOTDB-1149 Project: Apache IoTDB Issue Type: Bug Components: Client/CLI Affects Versions: 0.11.2 Reporter: 刘珍 start-cli.sh -e 'select statement' > result.out have to Press ENTER and complete the output. It is not user friendly. h1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1132) The password of create user statement contains a blank space can be created successfully and the user can login in database
刘珍 created IOTDB-1132: - Summary: The password of create user statement contains a blank space can be created successfully and the user can login in database Key: IOTDB-1132 URL: https://issues.apache.org/jira/browse/IOTDB-1132 Project: Apache IoTDB Issue Type: Bug Components: Server Environment: 0.11.3-SNAPSHOT Reporter: 刘珍 CREATE USER u_test 'write_ pwd' Msg: The statement is executed successfully. 密码中包含1个空格 用户u_test登陆数据库，输入密码（包含空格），成功。 用户手册： h3. 密码限制 IoTDB规定密码的字符长度不小于4，其中密码不能包含空格，密码采用MD5进行加密。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1284) unseq compaction file with time partition : java.io.IOException: Device {root.group_5.d_15} is not in tsFileMetaData
刘珍 created IOTDB-1284:
-
Summary: unseq compaction file with time partition :
java.io.IOException: Device {root.group_5.d_15} is not in tsFileMetaData
Key: IOTDB-1284
URL: https://issues.apache.org/jira/browse/IOTDB-1284
Project: Apache IoTDB
Issue Type: Bug
Components: Server
Reporter: 刘珍
0.11.3 9e371454b05f9a0e24fabb2c84f7ce690f14a882
iotdb config：
compaction_strategy=LEVEL_COMPACTION
enable_partition=true
partition_interval=3600
benchmark config：
OPERATION_PROPORTION=1:0:0:0:0:0:0:0:0:0:0
INSERT_MODE=session
#客户端和设备是否绑定，若为false则客户端数可以大于设备数
IS_CLIENT_BIND=true
#客户端并发数，若客户端和设备绑定，则必须小于等于设备数
CLIENT_NUMBER=10
#存储组数，必须小于等于设备数
GROUP_NUMBER=10
#总设备数
DEVICE_NUMBER=50
#每个设备的传感器数，总时间序列条数=DEVICE_NUMBER*SENSOR_NUMBER
SENSOR_NUMBER=50
#批写入数据行数，每行是某个设备所有传感器在某一时间戳的数据，每个batch写入数据点数=SENSOR_NUMBER*BATCH_SIZE
BATCH_SIZE=1000
#Total number of operations that each client process
LOOP=100
IS_OVERFLOW=true
OVERFLOW_MODE=0
OVERFLOW_RATIO=0.5
run test，iotdb log error:
java.io.IOException: Device \{root.group_5.d_15} is not in tsFileMetaData
at
org.apache.iotdb.tsfile.read.TsFileSequenceReader.readTimeseriesMetadata(TsFileSequenceReader.java:324)
at
org.apache.iotdb.tsfile.read.TsFileSequenceReader.getChunkMetadataList(TsFileSequenceReader.java:1153)
at org.apache.iotdb.db.utils.MergeUtils.buildMetaHeap(MergeUtils.java:187)
at org.apache.iotdb.db.utils.MergeUtils.collectUnseqChunks(MergeUtils.java:173)
at
org.apache.iotdb.db.engine.merge.manage.MergeResource.getUnseqReaders(MergeResource.java:163)
at
org.apache.iotdb.db.engine.merge.task.MergeMultiChunkTask.mergePaths(MergeMultiChunkTask.java:178)
at
org.apache.iotdb.db.engine.merge.task.MergeMultiChunkTask.mergeSeries(MergeMultiChunkTask.java:141)
at org.apache.iotdb.db.engine.merge.task.MergeTask.doMerge(MergeTask.java:152)
at org.apache.iotdb.db.engine.merge.task.MergeTask.call(MergeTask.java:100)
at org.apache.iotdb.db.engine.merge.task.MergeTask.call(MergeTask.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2021-04-07 11:39:53,763 [MergeThread-0] INFO
org.apache.iotdb.db.engine.compaction.TsFileManagement:382 - root.group_5 a
merge task abnormally ends
2021-04-07 11:39:53,878 [pool-7-IoTDB-RPC-Client-thread-13] INFO
org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor:1066 - will close
a false TsFile because too many active partitions (1 > 1) in the storage group
root.group_3,
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1275) backgroup exec for cli -e function causes an infinite loop in writing output file
刘珍 created IOTDB-1275:
-
Summary: backgroup exec for cli -e function causes an infinite
loop in writing output file
Key: IOTDB-1275
URL: https://issues.apache.org/jira/browse/IOTDB-1275
Project: Apache IoTDB
Issue Type: Bug
Components: Client/CLI
Reporter: 刘珍
0.11.3 9e371454b05f9a0e24fabb2c84f7ce690f14a882
set storage group root.db1;
CREATE TIMESERIES root.db1.tab1.id WITH DATATYPE=INT32, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.name WITH DATATYPE=text, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean, ENCODING=PLAIN
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),1,'lily',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),0,'lily0',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),1,'lily1',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),2,'lily2',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),3,'lily3',25,'usa',5678.34,7.77,false);
--.isnert 200 records
nohup ./sbin/start-cli.sh -e 'select id,name from root.db1.tab1' > a.out &
{color:#FF}a.out in an infinite loop :{color}
{color:#FF}Reach the max_display_num = 1000. Press ENTER to show more,
input 'q' to quit.{color}
{color:#FF}java.io.IOException: Bad file descriptor{color}
{color:#FF} at java.io.FileInputStream.readBytes(Native Method){color}
{color:#FF} at java.io.FileInputStream.read(FileInputStream.java:255){color}
{color:#FF} at
java.io.BufferedInputStream.read1(BufferedInputStream.java:284){color}
{color:#FF} at
java.io.BufferedInputStream.read(BufferedInputStream.java:345){color}
{color:#FF} at
sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284){color}
{color:#FF} at
sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326){color}
{color:#FF} at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178){color}
{color:#FF} at
java.io.InputStreamReader.read(InputStreamReader.java:184){color}
{color:#FF} at java.io.BufferedReader.fill(BufferedReader.java:161){color}
{color:#FF} at
java.io.BufferedReader.readLine(BufferedReader.java:324){color}
{color:#FF} at
java.io.BufferedReader.readLine(BufferedReader.java:389){color}
{color:#FF} at
org.apache.iotdb.cli.AbstractCli.executeQuery(AbstractCli.java:577){color}
{color:#FF} at
org.apache.iotdb.cli.AbstractCli.handleInputCmd(AbstractCli.java:434){color}
{color:#FF} at
org.apache.iotdb.cli.AbstractCli.processCommand(AbstractCli.java:750){color}
{color:#FF} at org.apache.iotdb.cli.Cli.serve(Cli.java:122){color}
{color:#FF} at org.apache.iotdb.cli.Cli.main(Cli.java:75){color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1274) ./sbin/start-cli.sh -e 'select last * from root.*' Parser error : Msg: 401
刘珍 created IOTDB-1274:
-
Summary: ./sbin/start-cli.sh -e 'select last * from root.*'
Parser error : Msg: 401
Key: IOTDB-1274
URL: https://issues.apache.org/jira/browse/IOTDB-1274
Project: Apache IoTDB
Issue Type: Bug
Components: Client/CLI
Reporter: 刘珍
0.11.3 9e371454b05f9a0e24fabb2c84f7ce690f14a882
{color:#FF}start-cli.sh -e SQL contains * parser error{color}
{color:#FF}Msg: 401: line 1:18 mismatched input 'conf' expecting \{FROM,
',', '.'}{color}
set storage group root.db1;
CREATE TIMESERIES root.db1.tab1.id WITH DATATYPE=INT32, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.name WITH DATATYPE=text, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean, ENCODING=PLAIN
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),1,'lily',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),2,'lily2',25,'usa',5678.34,7.77,false);
./sbin/start-cli.sh{color:#FF} -e{color} 'select last * from root.*'
Msg: 401: line 1:18 mismatched input 'conf' expecting \{FROM, ',', '.'}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1196) use this path ：paths.add(new Path("device_1.sensor_1")) for query and got java.lang.NullPointerException
刘珍 created IOTDB-1196:
-
Summary: use this path ：paths.add(new Path("device_1.sensor_1"))
for query and got java.lang.NullPointerException
Key: IOTDB-1196
URL: https://issues.apache.org/jira/browse/IOTDB-1196
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Java
Reporter: 刘珍
master branch
commit 6694c5d70ff78bd1b67768b147514ec57a168990
Author: Yifu Zhou
Date: Wed Mar 10 10:56:04 2021 +0800
Update the SeedUrl Format Exception Info when using cluster mode (#2786)
《IOTDB用户手册- 0.12-snapshot-20210305.pdf》 P115 7.6.2.4 读取现有 TsFile 示例
/**
* The class is to show how to read TsFile file named "test.tsfile". The TsFile
file "test.tsfile"
* is generated from class TsFileWriteWithTSRecord or TsFileWriteWithTablet. Run
* TsFileWriteWithTSRecord or TsFileWriteWithTablet to generate the test.tsfile
first
*/
Run this class，got the exception：
Exception in thread "main" java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:347)
at java.util.TreeMap.containsKey(TreeMap.java:232)
at
org.apache.iotdb.tsfile.read.controller.MetadataQuerierByFileImpl.loadChunkMetaDatas(MetadataQuerierByFileImpl.java:95)
at
org.apache.iotdb.tsfile.read.query.executor.TsFileExecutor.execute(TsFileExecutor.java:70)
at org.apache.iotdb.tsfile.read.ReadOnlyTsFile.query(ReadOnlyTsFile.java:47)
at org.apache.iotdb.tsfile.TsFileRead_pdf.queryAndPrint(TsFileRead_pdf.java:40)
at org.apache.iotdb.tsfile.TsFileRead_pdf.main(TsFileRead_pdf.java:59)
Change
"paths.add(new Path("device_1.sensor_1"));"
into
"paths.add(new Path("device_1", "sensor_1"));"
the result set is right.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1231) After load tsfile，this tsfile is rudely moved out of its location.
刘珍 created IOTDB-1231: - Summary: After load tsfile，this tsfile is rudely moved out of its location. Key: IOTDB-1231 URL: https://issues.apache.org/jira/browse/IOTDB-1231 Project: Apache IoTDB Issue Type: Bug Reporter: 刘珍 master branch. commit id :5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7 As title，the tsfile is users' *PRIVATE file* ,shouldn't be moved to another location without permission. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1232) import csv，the imported data is incompletely and some imported time column is wrong.
刘珍 created IOTDB-1232:
-
Summary: import csv，the imported data is incompletely and some
imported time column is wrong.
Key: IOTDB-1232
URL: https://issues.apache.org/jira/browse/IOTDB-1232
Project: Apache IoTDB
Issue Type: Bug
Reporter: 刘珍
Attachments: dump0.csv
master branch.
commit id : 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
iotdb cli :
SET STORAGE GROUP TO root.sg
CREATE TIMESERIES root.sg.d1.s1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
CREATE TIMESERIES root.sg.d1.s2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
dump0.csv:
[^dump0.csv]
./tools/import-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -f ./dump0.csv -tz
+08:00
--
Starting IoTDB Client Import Script
--
14:45:08.786 [main] DEBUG org.apache.iotdb.rpc.AutoResizingBuffer -
org.apache.iotdb.rpc.AutoResizingBuffer@cb5822 expand from 65536 to 16384000,
request: 16384000
Start to import data from: dump0.csv
Import from: dump0.csv 0% │ │ 0/41 (0:00:00 / ?) Importing...
Import from: dump0.csv 100%
││ 41/41 (0:00:00 /
0:00:00) Importing...
IoTDB> select s1 from root.sg.d1;
+-+-+
| Time|root.sg.d1.s1|
+-+-+
|2021-03-12T11:52:50.000+08:00| 0.757181|
|2021-03-12T11:53:02.000+08:00| 0.130961|
|2021-03-12T11:59:42.000+08:00| 0.866891|
|2021-03-12T11:59:45.000+08:00| 0.371016|
|2021-03-12T11:59:53.000+08:00| 0.079831|
+-+-+
Total line number = 5
*{color:#FF}expected :{color}*
Total line number = 39
*{color:#FF}and "2021-03-12T11:59:53.000+08:00" is not exist in
dump0.csv.{color}*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1229) load tsfile into iotdb ,which data contains the same name tsfile,records are not loaded successfully.
刘珍 created IOTDB-1229:
-
Summary: load tsfile into iotdb ,which data contains the same name
tsfile,records are not loaded successfully.
Key: IOTDB-1229
URL: https://issues.apache.org/jira/browse/IOTDB-1229
Project: Apache IoTDB
Issue Type: Bug
Components: Server
Reporter: 刘珍
master branch.
commit id : 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
iotdb cli:
SET STORAGE GROUP TO [root.sg|http://root.sg/]
CREATE TIMESERIES [root.sg|http://root.sg/].d1.s1 WITH DATATYPE=DOUBLE,
ENCODING=PLAIN
ll data/data/sequence/root.sg/0/0：
1615773108031-1-0.tsfile
1615773108031-1-0.tsfile.resource
source tsfile：
1615773108031-1-0.tsfile
which was generated from the following SQL:
SET STORAGE GROUP TO [root.sg|http://root.sg/]
CREATE TIMESERIES [root.sg|http://root.sg/].d1.s1 WITH DATATYPE=DOUBLE,
ENCODING=PLAIN
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:52:50.687+08:00, 0.338776);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:52:50.692+08:00, 0.250776);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:52:50.694+08:00, 0.575861);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:52:50.695+08:00, 0.229369);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:52:50.696+08:00, 0.149007);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:52:50.697+08:00, 0.182348);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:52:50.698+08:00, 0.334755);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:52:50.699+08:00, 0.757181);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:53:02.649+08:00, 0.618037);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:53:02.655+08:00, 0.789077);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:53:02.656+08:00, 0.797554);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:53:02.657+08:00, 0.660189);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:53:02.658+08:00, 0.70841);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:53:02.659+08:00, 0.09);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:53:02.660+08:00, 0.130961);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:42.835+08:00, 0.681662);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:42.840+08:00, 0.7779);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:42.841+08:00, 0.385094);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:42.842+08:00, 0.406137);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:42.843+08:00, 0.32487);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:42.844+08:00, 0.866891);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:45.601+08:00, 0.400888);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:45.606+08:00, 0.413434);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:45.607+08:00, 0.093675);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:45.608+08:00, 0.89578);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:45.609+08:00, 0.24261);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:45.610+08:00, 0.472395);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:45.611+08:00, 0.371016);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:53.051+08:00, 0.898205);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:53.056+08:00, 0.913098);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:53.057+08:00, 0.637392);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:53.058+08:00, 0.774389);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:53.059+08:00, 0.258826);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:53.060+08:00, 0.900979);
insert into [root.sg|http://root.sg/].d1(time,s1) values
(2021-03-12T11:59:53.061+08:00, 0.079831);
flush;
load this tsfile into iotdb：
load ".../data_0315/data/sequence/root.sg/0/0/1615773108031-1-0.tsfile" false;
Msg: The statement is executed successfully.
But:
IoTDB> select * from root.sg.d1.s1;
++
|Time|
++
++
*{color:#FF}Empty set.{color}*
Expected:
Total line number = 35
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1239) Incorrect datetime value can be inserted into iotdb successfully.
刘珍 created IOTDB-1239:
-
Summary: Incorrect datetime value can be inserted into iotdb
successfully.
Key: IOTDB-1239
URL: https://issues.apache.org/jira/browse/IOTDB-1239
Project: Apache IoTDB
Issue Type: Bug
Components: Server
Reporter: 刘珍
master branch.
commit id 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7 .
SET STORAGE GROUP TO root.sg
CREATE TIMESERIES root.sg.d1.s2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
insert into root.sg.d1(time,s2 ) values (15741792,8.76);
IoTDB> select * from root.sg.d1;
+---+-+
| Time|root.sg.d1.s2|
+---+-+
|{color:#FF}+{color}51853-10-03T00:00:{color:#FF}.0{color}+08:00|
8.76|
+---+-+
{color:#FF}should be give an error :{color}
{color:#FF}Incorrect datetime value {color}
IoTDB> select * from root.sg.d1 where time=51853-10-03T00:00:.0+08:00
Msg: 401: Error occurred while parsing SQL to physical plan: line 1:36
extraneous input '51853-10-03T00:00:' expecting \{NOW, TRUE, FALSE, '-', '.',
'NaN', INT, EXPONENT, DATETIME, DOUBLE_QUOTE_STRING_LITERAL,
SINGLE_QUOTE_STRING_LITERAL}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1192) JDBC: statement.execute ("sql;") if the sql end with semicolon ，Error occurred while parsing SQL to physical plan
刘珍 created IOTDB-1192:
-
Summary: JDBC: statement.execute ("sql;") if the sql end with
semicolon ，Error occurred while parsing SQL to physical plan
Key: IOTDB-1192
URL: https://issues.apache.org/jira/browse/IOTDB-1192
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Java
Reporter: 刘珍
《IOTDB用户手册- 0.12-snapshot-20210305.pdf》 P91 7.1.4
{color:#172b4d}Exception in thread "main" java.sql.BatchUpdateException: Error
occurred while parsing SQL to physical plan: line 1:47 token recognition error
at: ';'{color}
{color:#172b4d} at
org.apache.iotdb.jdbc.IoTDBStatement.executeBatchSQL(IoTDBStatement.java:293){color}
{color:#172b4d} at
org.apache.iotdb.jdbc.IoTDBStatement.executeBatch(IoTDBStatement.java:255){color}
{color:#172b4d} at jdbc.main.JDBCExample.main(JDBCExample.java:61){color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1211) create function [Reserved Words] ，The error message is not clear
刘珍 created IOTDB-1211:
-
Summary: create function [Reserved Words] ，The error message is
not clear
Key: IOTDB-1211
URL: https://issues.apache.org/jira/browse/IOTDB-1211
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Engine
Reporter: 刘珍
Attachments: image-2021-03-11-14-46-00-500.png
master branch
commit 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
Merge: 7f9 f63b849
Author: Xiangwei Wei <34242296+alima...@users.noreply.github.com>
Date: Thu Mar 4 15:57:38 2021 +0800
Merge pull request #2759 from apache/fixQueryInfoNull
[ISSUE-2758] NullPointerException in QueryTimeManager.checkQueryAlive()
IoTDB> CREATE FUNCTION {color:#FF}add{color} AS
"org.apache.iotdb.udf.Adder";
{color:#FF}Msg: 401: Error occurred while parsing SQL to physical plan:
line 1:16 mismatched input 'add' expecting ID{color}
{color:#FF}!image-2021-03-11-14-46-00-500.png!{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1220) MQTT insert 10 rows ，elapsed time is 5s ，and the inserted row count is less than 10.
刘珍 created IOTDB-1220:
-
Summary: MQTT insert 10 rows ，elapsed time is 5s ，and the inserted
row count is less than 10.
Key: IOTDB-1220
URL: https://issues.apache.org/jira/browse/IOTDB-1220
Project: Apache IoTDB
Issue Type: Bug
Components: Server
Reporter: 刘珍
master branch.
commit id :5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
## Usage
* Update configuration to enable MQTT service. (`enable_mqtt_service=true` in
iotdb-engine.properties)
* Launch the IoTDB server.
* Setup storage group `SET STORAGE GROUP TO root.sg` and create time timeseries
`CREATE TIMESERIES root.sg.d1.s1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN`.
* Run `org.apache.iotdb.mqtt.MQTTClient` to run the mqtt client and send events
to server.
cat ../../src/main/java/org/apache/iotdb/mqtt/MQTTClient.java
package org.apache.iotdb.mqtt;
import org.fusesource.mqtt.client.BlockingConnection;
import org.fusesource.mqtt.client.MQTT;
import org.fusesource.mqtt.client.QoS;
import java.util.Random;
public class MQTTClient {
public static void main(String[] args) throws Exception {
MQTT mqtt = new MQTT();
mqtt.setHost("127.0.0.1", 1883);
mqtt.setUserName("root");
mqtt.setPassword("root");
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
Random random = new Random();
for (int i = 0; i < 10; i++) {
String payload =
String.format(
"{\n"
+ "\"device\":\"root.sg.d1\",\n"
+ "\"timestamp\":%d,\n"
+ "\"measurements\":[\"s1\"],\n"
+ "\"values\":[%f]\n"
+ "}",
System.currentTimeMillis(), random.nextDouble());
connection.publish("root.sg.d1.s1", payload.getBytes(), QoS.AT_LEAST_ONCE,
false);
}
connection.disconnect();
}
}
run time java -classpath ".:" org/apache/iotdb/mqtt/MQTTClient
2 times,the elapsed time:
real 0m5.573s
user 0m0.352s
sys 0m0.055s
real 0m0.584s
user 0m0.371s
sys 0m0.039s
IoTDB> select s1 from root.sg.d1;
+-+-+
| Time|root.sg.d1.s1|
+-+-+
|2021-03-12T11:52:50.687+08:00| 0.338776|
|2021-03-12T11:52:50.692+08:00| 0.250776|
|2021-03-12T11:52:50.694+08:00| 0.575861|
|2021-03-12T11:52:50.695+08:00| 0.229369|
|2021-03-12T11:52:50.696+08:00| 0.149007|
|2021-03-12T11:52:50.697+08:00| 0.182348|
|2021-03-12T11:52:50.698+08:00| 0.334755|
|2021-03-12T11:52:50.699+08:00| 0.757181|
|2021-03-12T11:53:02.649+08:00| 0.618037|
|2021-03-12T11:53:02.655+08:00| 0.789077|
|2021-03-12T11:53:02.656+08:00| 0.797554|
|2021-03-12T11:53:02.657+08:00| 0.660189|
|2021-03-12T11:53:02.658+08:00| 0.70841|
|2021-03-12T11:53:02.659+08:00| 0.09|
|2021-03-12T11:53:02.660+08:00| 0.130961|
+-+-+
Total line number = 15
It costs 0.014s
the "Total line number" should be 20.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1216) User with 'READ_TIMESERIES' privilege execute UDTF query , "Msg: 602: No permissions for this operation UDTF"
刘珍 created IOTDB-1216:
-
Summary: User with 'READ_TIMESERIES' privilege execute UDTF query
, "Msg: 602: No permissions for this operation UDTF"
Key: IOTDB-1216
URL: https://issues.apache.org/jira/browse/IOTDB-1216
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Engine
Reporter: 刘珍
Attachments: image-2021-03-11-17-45-21-522.png
master branch
commit id : 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
root connect iotdb:
SET STORAGE GROUP TO root.sg3;
CREATE TIMESERIES root.sg3.d1.s1 WITH DATATYPE=INT32, ENCODING=PLAIN;
CREATE TIMESERIES root.sg3.d1.s2 WITH DATATYPE=INT32, ENCODING=PLAIN;
INSERT INTO root.sg3.d1(timestamp, s1, s2) VALUES (10, -11, 11);
INSERT INTO root.sg3.d1(timestamp, s1, s2) VALUES (11, -12, 12);
INSERT INTO root.sg3.d1(timestamp, s1, s2) VALUES (12, -13, 13);
CREATE USER ln_write_user 'write_pwd'
grant user ln_write_user privileges 'READ_TIMESERIES' on root.sg3;
ln_write_user connect iotdb to execute UDTF(max) query:
select max(s1) from root.sg3.d1;
{color:#FF}Msg: 602: No permissions for this operation UDTF{color}
!image-2021-03-11-17-45-21-522.png!
Max.java :
package org.apache.iotdb.udf;
import org.apache.iotdb.db.query.udf.api.UDTF;
import org.apache.iotdb.db.query.udf.api.access.Row;
import org.apache.iotdb.db.query.udf.api.collector.PointCollector;
import org.apache.iotdb.db.query.udf.api.customizer.config.UDTFConfigurations;
import org.apache.iotdb.db.query.udf.api.customizer.parameter.UDFParameters;
import
org.apache.iotdb.db.query.udf.api.customizer.strategy.RowByRowAccessStrategy;
import org.apache.iotdb.tsfile.file.metadata.enums.TSDataType;
import java.io.IOException;
public class Max implements UDTF {
private Long time;
private int value;
@Override
public void beforeStart(UDFParameters parameters, UDTFConfigurations
configurations) {
configurations
.setOutputDataType(TSDataType.INT32)
.setAccessStrategy(new RowByRowAccessStrategy());
}
@Override
public void transform(Row row, PointCollector collector) {
int candidateValue = row.getInt(0);
if (time == null || value < candidateValue) {
time = row.getTime();
value = candidateValue;
}
}
@Override
public void terminate(PointCollector collector) throws IOException {
if (time != null) {
collector.putInt(time, value);
}
}
create function max as "org.apache.iotdb.udf.Max";
}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1212) select sin(not_exist) from root.sg1.d1; The error message is not right.
刘珍 created IOTDB-1212:
-
Summary: select sin(not_exist) from root.sg1.d1; The error
message is not right.
Key: IOTDB-1212
URL: https://issues.apache.org/jira/browse/IOTDB-1212
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Java
Reporter: 刘珍
master branch
commit id : 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
SET STORAGE GROUP TO root.sg1;
CREATE TIMESERIES root.sg1.d1.s1 WITH DATATYPE=INT32, ENCODING=PLAIN;
CREATE TIMESERIES root.sg1.d1.s2 WITH DATATYPE=INT32, ENCODING=PLAIN;
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (0, -1, 1);
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (1, -2, 2);
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (2, -3, 3);
select sin(not_exist) from root.sg1.d1;
Msg: 411: Error occurred in query process: Error occurred during executing
UDTF#validate(UDFParameterValidator):
{color:#FF}org.apache.iotdb.db.query.udf.api.exception.UDFInputSeriesNumberNotValidException:
the number of the input series is not valid. expected: 1. actual: 0.{color}
{color:#FF}The error message is not right.{color}
{color:#ff}The actual is the input series does not exist.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1213) Flink-IoTDB document in English and Chinese
赵家贝 created IOTDB-1213: -- Summary: Flink-IoTDB document in English and Chinese Key: IOTDB-1213 URL: https://issues.apache.org/jira/browse/IOTDB-1213 Project: Apache IoTDB Issue Type: Improvement Components: site Reporter: 赵家贝 Fix For: master branch Add Flink-IoTDB documents to website and doc. The documents include English and Chinese version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1214) Flink-IoTDB document in English and Chinese
赵家贝 created IOTDB-1214: -- Summary: Flink-IoTDB document in English and Chinese Key: IOTDB-1214 URL: https://issues.apache.org/jira/browse/IOTDB-1214 Project: Apache IoTDB Issue Type: Improvement Components: site Reporter: 赵家贝 Fix For: master branch Add Flink IoTDB documents to website and docs. The documents include English and Chinese version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1178) Data loss when tsfile merge failed
[ https://issues.apache.org/jira/browse/IOTDB-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17297072#comment-17297072 ] 张凌哲 commented on IOTDB-1178: fixed in [PR-2707|https://github.com/apache/iotdb/pull/2707] > Data loss when tsfile merge failed > --- > > Key: IOTDB-1178 > URL: https://issues.apache.org/jira/browse/IOTDB-1178 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Engine >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Blocker > Fix For: 0.12.0, 0.11.3 > > > An error is reported during file merging. The new file is not generated and > the old file is deleted. > current problem: > 1. when delete tsfile, if tsfile is reading now, will throw exception... > 2. do not deal after exception catch, and then lead to delete old file. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1294) seq ingestion，delete a sensor point from a level 0 tsfile which is compacting into level 1,... after compact this tsfile into level 2 ,the deleted sensor point could be
刘珍 created IOTDB-1294: - Summary: seq ingestion，delete a sensor point from a level 0 tsfile which is compacting into level 1,... after compact this tsfile into level 2 ,the deleted sensor point could be queried successfully Key: IOTDB-1294 URL: https://issues.apache.org/jira/browse/IOTDB-1294 Project: Apache IoTDB Issue Type: Bug Reporter: 刘珍 Attachments: image-2021-04-09-17-49-08-467.png, image-2021-04-09-17-51-26-322.png, image-2021-04-09-17-52-10-010.png, image-2021-04-09-17-54-49-511.png, image-2021-04-09-17-55-13-818.png, image-2021-04-09-17-56-00-789.png, image-2021-04-09-17-58-46-226.png benchmark run sequence ingestion start-cli execute delete and select statement : delete a sensor point from a level 0 tsfile which is compacting into level 1(eg 1617959150884-7-0.tsfile,print-tsfile-sketch.sh工具获取此tsfile中的time range), !image-2021-04-09-17-49-08-467.png! !image-2021-04-09-17-55-13-818.png! .. after compact this tsfile into level 2 ,the deleted sensor point could be queried successfully： !image-2021-04-09-17-56-00-789.png! !image-2021-04-09-17-58-46-226.png! benchmark： INSERT_MODE=session #客户端和设备是否绑定，若为false则客户端数可以大于设备数 IS_CLIENT_BIND=true #客户端并发数，若客户端和设备绑定，则必须小于等于设备数 CLIENT_NUMBER=10 #存储组数，必须小于等于设备数 GROUP_NUMBER=10 #总设备数 DEVICE_NUMBER=50 #每个设备的传感器数，总时间序列条数=DEVICE_NUMBER*SENSOR_NUMBER SENSOR_NUMBER=500 #批写入数据行数，每行是某个设备所有传感器在某一时间戳的数据，每个batch写入数据点数=SENSOR_NUMBER*BATCH_SIZE BATCH_SIZE=100 #Total number of operations that each client process LOOP=1 IS_OVERFLOW=false -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1293) There is data in iotdb modify parameter enable_partition=true ,restart iotdb ,the error message is not clear
刘珍 created IOTDB-1293:
-
Summary: There is data in iotdb modify parameter
enable_partition=true ,restart iotdb ,the error message is not clear
Key: IOTDB-1293
URL: https://issues.apache.org/jira/browse/IOTDB-1293
Project: Apache IoTDB
Issue Type: Bug
Reporter: 刘珍
0.11.3 9e371454b05f9a0e24fabb2c84f7ce690f14a882
There is data in iotdb modify enable_partition=true ,restart iotdb,the error
message is not clear:
2021-04-06 10:47:49,407 [main] ERROR
org.apache.iotdb.db.conf.IoTDBConfigCheck:306 - Wrong
partition_interval,{color:#FF} please set as: 9223372036854775807 !{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1316) A sensor point value is invalid and this row can be imported successfully，but the following rows in this file are not executed
刘珍 created IOTDB-1316:
-
Summary: A sensor point value is invalid and this row can be
imported successfully，but the following rows in this file are not executed
Key: IOTDB-1316
URL: https://issues.apache.org/jira/browse/IOTDB-1316
Project: Apache IoTDB
Issue Type: Bug
Reporter: 刘珍
Attachments: image-2021-04-19-17-50-27-843.png
release 0.12.0
A sensor point value is invalid and this row can be imported successfully( the
sensor point is null)，but the following rows in this file are not executed。
cli execute :
{color:#172b4d}CREATE TIMESERIES
{color}[{color:#0052cc}root.db1.tab1.id{color}|http://root.db1.tab1.id/]{color:#172b4d}
WITH DATATYPE=INT32, ENCODING=PLAIN{color}
{color:#172b4d}CREATE TIMESERIES
{color}[{color:#0052cc}root.db1.tab1.name{color}|http://root.db1.tab1.name/]{color:#172b4d}
WITH DATATYPE=text, ENCODING=PLAIN{color}
{color:#172b4d}CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32,
ENCODING=PLAIN{color}
{color:#172b4d}CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text,
ENCODING=PLAIN{color}
{color:#172b4d}CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float,
ENCODING=PLAIN{color}
{color:#172b4d}CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double,
ENCODING=PLAIN{color}
{color:#172b4d}CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean,
ENCODING=PLAIN{color}
{color:#172b4d} {color}
2 import files locate in csv_file directory :
*cat csv_file/dump_ts3.csv :*
Time,root.db1.tab1.country,root.db1.tab1.other,root.db1.tab1.student,root.db1.tab1.name,root.db1.tab1.id,root.db1.tab1.salary,root.db1.tab1.age
2021-04-19T16:28:19,usa,china,false,丽丽,1.0,5678.34,25.0
2021-04-19T16:28:29,usa,7.77,false,支持,0.0,5678.34,25.0
2021-04-19T16:28:39,usa,7.77,false,lily,1.0,5678.34,25.0
2021-04-19T16:28:49,usa,7.77,false,lily2,2.0,5678.34,25.0
2021-04-19T16:28:59,usa,7.77,false,lily3,3.0,5678.34,25.0
*cat csv_file/dump_ts4.csv :*
Time,root.db1.tab1.country,root.db1.tab1.other,root.db1.tab1.student,root.db1.tab1.name,root.db1.tab1.id,root.db1.tab1.salary,root.db1.tab1.age
2021-04-19T16:29:19,usa,7.77,false,lily,1.0,5678.34,25.0
2021-04-19T16:29:29,usa,7.77,false,lily0,0.0,5678.34,25.0
2021-04-19T16:29:39,usa,7.77,false,lily1,1.0,5678.34,25.0
2021-04-19T16:29:49,usa,7.77,false,lily2,2.0,5678.34,25.0
2021-04-19T16:29:59,usa,7.77,false,lily3,3.0,5678.34,25.0
import SQL:
./import-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -f ./csv_file
--
Starting IoTDB Client Import Script
--
Start to import data from: dump_ts3.csv
Import from: dump_ts3.csv 0% │ │ 0/7 (0:00:00 / ?) Importing...
Meet error when insert csv because
org.apache.iotdb.db.exception.StorageEngineException: failed to insert
measurements [other] {color:#FF}caused by For input string: "china";{color}
Start to import data from: dump_ts4.csv
Import from: dump_ts4.csv 0% │ │ 0/7 (0:00:00 / ?) Importing...
Import from: dump_ts4.csv 100%
│█│ 7/7 (0:00:00 /
0:00:00) Importing...
cli:
select * from root.db1.*;
!image-2021-04-19-17-50-27-843.png!
The last 4 rows in dump_ts3.csv are not imported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1315) export-csv.sh -tf yyyy-MM-dd\'T\'HH:mm:ss.SSSZ error： is not supported
刘珍 created IOTDB-1315:
-
Summary: export-csv.sh -tf -MM-dd\'T\'HH:mm:ss.SSSZ error：
is not supported
Key: IOTDB-1315
URL: https://issues.apache.org/jira/browse/IOTDB-1315
Project: Apache IoTDB
Issue Type: Bug
Reporter: 刘珍
Attachments: image-2021-04-19-17-33-31-547.png,
image-2021-04-19-17-34-40-690.png, image-2021-04-19-17-36-01-620.png
release 0.12.0
cli execute ：
CREATE TIMESERIES [root.db1.tab1.id|http://root.db1.tab1.id/] WITH
DATATYPE=INT32, ENCODING=PLAIN
CREATE TIMESERIES [root.db1.tab1.name|http://root.db1.tab1.name/] WITH
DATATYPE=text, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean, ENCODING=PLAIN
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),1,'lily',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),0,'lily0',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),1,'lily1',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),2,'lily2',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),3,'lily3',25,'usa',5678.34,7.77,false);
select file ：
select * from root.db1.*
execute export indicate ts format ：
./export-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -tf
{color:#FF}-MM-dd\'T\'HH:mm:ss.SSSZ{color} -td ./ -f dump_ts4 -s select
--
Starting IoTDB Client Export Script
--
Input time format -MM-dd'T'HH:mm:ss.SSSZ {color:#FF}is not
supported{color}, please input like -MM-dd\ HH:mm:ss.SSS or
-MM-dd'T'HH:mm:ss.SSS
SimpleDateFormat中支持了，但是
!image-2021-04-19-17-33-31-547.png!
这个里面没有加：
!image-2021-04-19-17-36-01-620.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1313) import-csv can not indicate timestamp format，this causes millisecond is zero
刘珍 created IOTDB-1313:
-
Summary: import-csv can not indicate timestamp format，this causes
millisecond is zero
Key: IOTDB-1313
URL: https://issues.apache.org/jira/browse/IOTDB-1313
Project: Apache IoTDB
Issue Type: Bug
Reporter: 刘珍
Attachments: image-2021-04-19-16-58-15-628.png
release 0.12.0
cli构造数据:
构造数据：
CREATE TIMESERIES [root.db1.tab1.id|http://root.db1.tab1.id/] WITH
DATATYPE=INT32, ENCODING=PLAIN
CREATE TIMESERIES [root.db1.tab1.name|http://root.db1.tab1.name/] WITH
DATATYPE=text, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.age WITH DATATYPE=INT32, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.country WITH DATATYPE=text, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.salary WITH DATATYPE=float, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.other WITH DATATYPE=double, ENCODING=PLAIN
CREATE TIMESERIES root.db1.tab1.student WITH DATATYPE=boolean, ENCODING=PLAIN
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),1,'lily',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),0,'lily0',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),1,'lily1',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),2,'lily2',25,'usa',5678.34,7.77,false);
insert into root.db1.tab1(time,id,name,age,country,salary,other ,student )
values(now(),3,'lily3',25,'usa',5678.34,7.77,false);
先export：
select文件的内容：select * from root.db1.*
./export-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -tf
{color:#FF}-MM-dd\'T\'HH:mm:ss.SSS{color} -td ./ -f dump_ts2.csv -s
select
导出文件指定tf包含毫秒。导出结果：
Time,root.db1.tab1.country,root.db1.tab1.other,root.db1.tab1.student,root.db1.tab1.name,root.db1.tab1.id,root.db1.tab1.salary,root.db1.tab1.age
2021-04-19T16:28:49{color:#FF}.810{color},usa,7.77,false,lily,1.0,5678.34,25.0
2021-04-19T16:28:49.818,usa,7.77,false,lily0,0.0,5678.34,25.0
2021-04-19T16:28:49.824,usa,7.77,false,lily1,1.0,5678.34,25.0
2021-04-19T16:28:49.828,usa,7.77,false,lily2,2.0,5678.34,25.0
2021-04-19T16:28:49.833,usa,7.77,false,lily3,3.0,5678.34,25.0
cli删除数据：
delete from root.db1.*;
import导入数据：
./import-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -f ./dump_ts2.csv0.csv
cli查询：
select * from root.db1.*; --毫秒被截断置为0 ，import-csv不支持指定时间戳格式。
!image-2021-04-19-16-58-15-628.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1579) JDBC connection failed: enable rpcThriftCompressionEnable
张洪胤 created IOTDB-1579: -- Summary: JDBC connection failed: enable rpcThriftCompressionEnable Key: IOTDB-1579 URL: https://issues.apache.org/jira/browse/IOTDB-1579 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Fix For: 0.12.0 Firstly, I set org.apache.iotdb.jdbc.Config.rpcThriftCompressionEnable = true; in code, then I use DriverManager.getConnection() to connect, but it failed. Some logs: org.apache.iotdb.rpc.IoTDBConnectionException: org.apache.thrift.transport.TTransportException: Socket is closed by peer. java.sql.SQLException: Can not establish connection with jdbc:iotdb://127.0.0.1:6667/ : Socket is closed by peer.. cn.edu.tsinghua.iotdb.benchmark.tsdb.TsdbException: cn.edu.tsinghua.iotdb.benchmark.tsdb.TsdbException: java.sql.SQLException: Can not establish connection with jdbc:iotdb://127.0.0.1:6667/ : Socket is closed by peer.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1591) release-0.12.2 RC1 cluster : Execute CREATE FUNCTION on 1 node, this FUNCTION is invisible to other nodes
[
https://issues.apache.org/jira/browse/IOTDB-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17405526#comment-17405526
]
刘珍 commented on IOTDB-1591:
---
This is not a bug.
It's need to copy ${UDF}.jar to all nodes .(ext/udf)
> release-0.12.2 RC1 cluster : Execute CREATE FUNCTION on 1 node, this
> FUNCTION is invisible to other nodes
> --
>
> Key: IOTDB-1591
> URL: https://issues.apache.org/jira/browse/IOTDB-1591
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 0.12.2
>Reporter: 刘珍
>Priority: Minor
> Attachments: image-2021-08-26-13-51-54-754.png,
> udf-example-0.12.2-SNAPSHOT.jar
>
>
> iotdb info:
> release 0.12.2 RC1
> cluster :
> ip5/ip10/ip13
> default_replica_num=1
> ip13 :
> cp udf-example-0.12.2-SNAPSHOT.jar${release_1202_dir}/ext/udf/
> ip13 cli ：
> CREATE FUNCTION example AS "org.apache.iotdb.udf.UDTFExample"
> SHOW FUNCTIONS;
> !image-2021-08-26-13-51-54-754.png!
> ip5/ip10 cli:
> SHOW FUNCTIONS;
>
> FUNCTION example is invisible .
> ./sbin/start-cli.sh -h 192.168.130.10 -p 6688 -e "SELECT s1,
> example(s1), s2, example(s2) FROM root.sg1.d1;"
> Msg: 411: Error occurred in query process: Failed to reflect UDF instance,
> because UDF EXAMPLE {color:#DE350B}*has not been registered.*{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1590) release-0.12.2 RC1 cluster - count devices not consistent
刘珍 created IOTDB-1590: - Summary: release-0.12.2 RC1 cluster - count devices not consistent Key: IOTDB-1590 URL: https://issues.apache.org/jira/browse/IOTDB-1590 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Affects Versions: 0.12.2 Reporter: 刘珍 Attachments: config.properties, image-2021-08-26-11-13-04-210.png iotdb info : release 0.12.2 RC1 conf/iotdb-cluster.properties : seed_nodes=192.168.130.5:9005,192.168.130.10:9010,192.168.130.13:9013 default_replica_num=1 benchmark create 2000 devices . cli execute "count devices" on 3 nodes ,the result is inconsistent : [iotdb@fit05 release_1202]$ ./sbin/start-cli.sh -h 192.168.130.5 -p 6688 -e "count devices" +---+ |devices| +---+ |640| +---+ Total line number = 1 It costs 0.065s [iotdb@fit05 release_1202]$ ./sbin/start-cli.sh -h 192.168.130.10 -p 6688 -e "count devices" +---+ |devices| +---+ |720| +---+ Total line number = 1 It costs 0.079s [iotdb@fit05 release_1202]$ ./sbin/start-cli.sh -h 192.168.130.13 -p 6688 -e "count devices" +---+ |devices| +---+ |640| +---+ !image-2021-08-26-11-13-04-210.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1591) release-0.12.2 RC1 cluster : Execute CREATE FUNCTION on 1 node, this FUNCTION is invisible to other nodes
刘珍 created IOTDB-1591:
-
Summary: release-0.12.2 RC1 cluster : Execute CREATE FUNCTION on 1
node, this FUNCTION is invisible to other nodes
Key: IOTDB-1591
URL: https://issues.apache.org/jira/browse/IOTDB-1591
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.12.2
Reporter: 刘珍
Attachments: image-2021-08-26-13-51-54-754.png,
udf-example-0.12.2-SNAPSHOT.jar
iotdb info:
release 0.12.2 RC1
cluster :
ip5/ip10/ip13
default_replica_num=1
ip13 :
cp udf-example-0.12.2-SNAPSHOT.jar${release_1202_dir}/ext/udf/
ip13 cli ：
CREATE FUNCTION example AS "org.apache.iotdb.udf.UDTFExample"
SHOW FUNCTIONS;
!image-2021-08-26-13-51-54-754.png!
ip5/ip10 cli:
SHOW FUNCTIONS;
FUNCTION example is invisible .
./sbin/start-cli.sh -h 192.168.130.10 -p 6688 -e "SELECT s1, example(s1),
s2, example(s2) FROM root.sg1.d1;"
Msg: 411: Error occurred in query process: Failed to reflect UDF instance,
because UDF EXAMPLE {color:#DE350B}*has not been registered.*{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1599) Make SessionPool interface more adaptable to the cluster
刘珍 created IOTDB-1599:
-
Summary: Make SessionPool interface more adaptable to the cluster
Key: IOTDB-1599
URL: https://issues.apache.org/jira/browse/IOTDB-1599
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Java, Core/Cluster
Affects Versions: 0.12.2
Reporter: 刘珍
https://issues.apache.org/jira/browse/IOTDB-1399
Make session and jdbc interface more adaptable to the cluster
{color:#DE350B}*SessionPool should also be supported*{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1658) 0.12.2 RC2：The export-csv.sh tool does not support background running
刘珍 created IOTDB-1658:
-
Summary: 0.12.2 RC2：The export-csv.sh tool does not support
background running
Key: IOTDB-1658
URL: https://issues.apache.org/jira/browse/IOTDB-1658
Project: Apache IoTDB
Issue Type: Bug
Components: Tools/Others
Reporter: 刘珍
Attachments: image-2021-09-09-11-01-01-256.png
/data/liuzhen_test/RC2_no_comp/tools/export-csv.sh -h 127.0.0.1 -p 6667 -u root
-pw root -td /data/liuzhen_test/RC2_comp/test_shell/test_exp -f test_2_ -s
/data/liuzhen_test/RC2_comp/test_shell/sql/2.sql {color:#DE350B}*&*{color}
!image-2021-09-09-11-01-01-256.png|thumbnail!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1670) IoTDB: timestamp_precision=ns ； ./sbin/start-cli.sh -e "...where time=[ timestamp in number ]"，the query result is incorrect
[
https://issues.apache.org/jira/browse/IOTDB-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17413021#comment-17413021
]
刘珍 commented on IOTDB-1670:
---
This issue has been resolved.
> IoTDB: timestamp_precision=ns ； ./sbin/start-cli.sh -e "...where time=[
> timestamp in number ]"，the query result is incorrect
> -
>
> Key: IOTDB-1670
> URL: https://issues.apache.org/jira/browse/IOTDB-1670
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/CLI
>Affects Versions: master branch, 0.12.2
>Reporter: 刘珍
>Assignee: Haonan Hou
>Priority: Minor
> Labels: pull-request-available
> Attachments: screenshot-2.png
>
>
>
> iotdb config：
> timestamp_precision=ns
> CREATE TIMESERIES root.sg.dev.s_0 WITH DATATYPE=INT32, ENCODING=PLAIN;
> insert into root.sg.dev(time,s_0) values(163059601368534,357)
> IoTDB> select * from root.sg.dev where time=163059601368534
> +---+---+
> | Time|root.sg.dev.s_0|
> +---+---+
> |2021-09-02T23:20:13.68534+08:00|357|
> +---+---+
> Total line number = 1
> Run the start-cli.sh command to specify the -e parameter. {color:#DE350B}*The
> result is incorrect:*{color}
> [cluster@i-uishrrtq release_1202]$ ./sbin/start-cli.sh -e "select s_0 from
> root.sg.dev where time=163059601368534"
> +--+---+
> | Time|root.sg.dev.s_0|
> +--+---+
> |+51673500-09-09T14:.03443:20+08:00|357|
> +------+---+
> Total line number = 1
> !screenshot-2.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1604) new compaction schedule module
[
https://issues.apache.org/jira/browse/IOTDB-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414078#comment-17414078
]
刘珍 commented on IOTDB-1604:
---
1. 2021-09-13
commit 5127a32c5d0b5f8b1cf7f94a1363cc315c98f4bd
问题 1：重启合并后，多数据。
步骤1：copy 备份数据(合并时停止数据库的数据备份，10sg/100dev/每个dev 包含1
sensor/每个sensor1亿points)，到被测iotdb；启动数据库，日志出现enjoy；执行100条count查询，查询结果正确。
步骤2：不做其他操作，只让数据库执行合并。17小时40分钟后，合并完成（有遗留不符合合并条件的tsfile）。执行100条count查询，查询结果有31条记录{color:#DE350B}多数据{color}。
问题2：
new_compaction 第1个小时的写入性能高，第2个小时的写入性能下降明显。需分析。
按照旭鑫的建议调整iotdb配置参数：max_compaction_candidate_file_num = 50 ；
concurrent_compaction_thread=50，写入性能下降，见下图
!screenshot-1.png!
配置参数： [^配置参数.zip]
> new compaction schedule module
> --
>
> Key: IOTDB-1604
> URL: https://issues.apache.org/jira/browse/IOTDB-1604
> Project: Apache IoTDB
> Issue Type: New Feature
>Reporter: Hai Liu
>Assignee: Liuxuxin
>Priority: Major
> Attachments: screenshot-1.png
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1653) 重启写入下降10%
[ https://issues.apache.org/jira/browse/IOTDB-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414840#comment-17414840 ] 刘珍 commented on IOTDB-1653: --- 20210914 iotdb数据库版本Release 0.12.2 RC2 重启写入性能下降与开合并有关。 关闭合并，重启写入性能无下降。 !screenshot-1.png! 测试结果： RC2_开合并 RC2_关合并 干净环境-1 3986835 4483295 2 4219655 4361038 3 3969854 4376192 4 4162353 4342190 5 4172818 4330612 6 4302789 4379742 7 4327682 4460844 8 4123899 4416608 9 4304191 4442587 10 4282845 4419513 11 4128756 4420289 重启1-12 3353351 4353159 13 3422476 4275410 14 3304507 4310249 15 3965165 4269234 16 4257642 4228388 17 3901176 4236597 18 4254645 4222791 19 3949994 4223558 20 4267757 4304385 21 4056698 4287187 重启2-22 3342509 4419334 23 3319793 4282566 24 3385434 4334639 25 3967075 4281563 26 4174870 4254805 27 4043678 4258686 28 4259476 4244453 29 3956854 4267163 30 4261901 4331500 测试配置： [^配置参数.zip] > 重启写入下降10% > - > > Key: IOTDB-1653 > URL: https://issues.apache.org/jira/browse/IOTDB-1653 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Hai Liu >Assignee: Steve Yurong Su >Priority: Major > Attachments: screenshot-1.png, 配置参数.zip, 配置参数.zip > > Original Estimate: 16h > Remaining Estimate: 16h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1604) new compaction schedule module
[ https://issues.apache.org/jira/browse/IOTDB-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414852#comment-17414852 ] 刘珍 commented on IOTDB-1604: --- 20210914 new_compaction v3 commit 646a35093060cb67bb57183e7df2446434d50ca8 合并慢，查看1个sg的合并情况，5个多小时，只合并1.8G io低，基本看不到。旭鑫排查死锁情况。 !screenshot-3.png! > new compaction schedule module > -- > > Key: IOTDB-1604 > URL: https://issues.apache.org/jira/browse/IOTDB-1604 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Hai Liu >Assignee: Liuxuxin >Priority: Major > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > 配置参数.zip > > Original Estimate: 48h > Remaining Estimate: 48h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1692) LIKE query：The matching string contains “\n”. No result can be found
刘珍 created IOTDB-1692:
-
Summary: LIKE query：The matching string contains “\n”. No result
can be found
Key: IOTDB-1692
URL: https://issues.apache.org/jira/browse/IOTDB-1692
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Affects Versions: 0.12.2
Reporter: 刘珍
release 0.12.2 RC3
set storage group to root.liketest;
CREATE TIMESERIES root.liketest.dev1.s_1 WITH DATATYPE=TEXT, ENCODING=PLAIN;
insert into root.liketest.dev1(time,s_1) values(1,'fix\nxyz')
select * from root.liketest.dev1 where s_1 like 'fix\nxyz'
{color:#DE350B}*Empty set.*{color}
select * from root.liketest.dev1 where s_1 = 'fix\nxyz'
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1579) JDBC connection failed: enable rpcThriftCompressionEnable
[ https://issues.apache.org/jira/browse/IOTDB-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17416596#comment-17416596 ] 张洪胤 commented on IOTDB-1579: Yes, I try to set rpc_thrift_compression_enable=true in iotdb-engine.properties, and this surely solve this problem, thanks for your solution! > JDBC connection failed: enable rpcThriftCompressionEnable > - > > Key: IOTDB-1579 > URL: https://issues.apache.org/jira/browse/IOTDB-1579 > Project: Apache IoTDB > Issue Type: Bug > Components: Client/JDBC >Reporter: 张洪胤 >Priority: Major > Labels: easy-fix > > Firstly, I set org.apache.iotdb.jdbc.Config.rpcThriftCompressionEnable = > true; in code, then I use DriverManager.getConnection() to connect, but it > failed. > Some logs: > org.apache.iotdb.rpc.IoTDBConnectionException: > org.apache.thrift.transport.TTransportException: Socket is closed by peer. > java.sql.SQLException: Can not establish connection with > jdbc:iotdb://127.0.0.1:6667/ : Socket is closed by peer.. > cn.edu.tsinghua.iotdb.benchmark.tsdb.TsdbException: > cn.edu.tsinghua.iotdb.benchmark.tsdb.TsdbException: java.sql.SQLException: > Can not establish connection with jdbc:iotdb://127.0.0.1:6667/ : Socket is > closed by peer.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1579) JDBC connection failed: enable rpcThriftCompressionEnable
[ https://issues.apache.org/jira/browse/IOTDB-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1579: -- Assignee: 张洪胤 Resolution: Fixed This problem is caused by the setting of iotdb-engine.properties. This problem will be solved if rpc_thrift_compression_enable is set with value of true > JDBC connection failed: enable rpcThriftCompressionEnable > - > > Key: IOTDB-1579 > URL: https://issues.apache.org/jira/browse/IOTDB-1579 > Project: Apache IoTDB > Issue Type: Bug > Components: Client/JDBC >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Labels: easy-fix > > Firstly, I set org.apache.iotdb.jdbc.Config.rpcThriftCompressionEnable = > true; in code, then I use DriverManager.getConnection() to connect, but it > failed. > Some logs: > org.apache.iotdb.rpc.IoTDBConnectionException: > org.apache.thrift.transport.TTransportException: Socket is closed by peer. > java.sql.SQLException: Can not establish connection with > jdbc:iotdb://127.0.0.1:6667/ : Socket is closed by peer.. > cn.edu.tsinghua.iotdb.benchmark.tsdb.TsdbException: > cn.edu.tsinghua.iotdb.benchmark.tsdb.TsdbException: java.sql.SQLException: > Can not establish connection with jdbc:iotdb://127.0.0.1:6667/ : Socket is > closed by peer.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1604) new compaction schedule module
[
https://issues.apache.org/jira/browse/IOTDB-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17415329#comment-17415329
]
刘珍 commented on IOTDB-1604:
---
20210915
new_compaction分支V2版本，关合并，生成数据：10sg/100dev/每个dev
6个sensor,顺序数据，执行2遍（起始时间戳有偏移），产生乱序，每个sensor有2亿点。
new_compaction分支V3版本，开启合并，在上面的data上执行合并：{color:red}20小时30分钟java.lang.OutOfMemoryError:
GC overhead limit exceeded{color}
2021-09-15 08:00:16,818 [pool-24-thread-1] ERROR
o.a.i.d.c.IoTDBDefaultThreadExceptionHandler:31 - Exception in thread
pool-24-thread-1-51
java.lang.OutOfMemoryError: GC overhead limit exceeded
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1855)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2068)
at
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
at
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2021-09-15 08:00:16,818 [pool-25-thread-1] ERROR
o.a.i.d.c.IoTDBDefaultThreadExceptionHandler:31 - Exception in thread
pool-25-thread-1-52
java.lang.OutOfMemoryError: GC overhead limit exceeded
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.addConditionWaiter(AbstractQueuedSynchronizer.java:1855)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2068)
at
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
at
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
关合并，开合并的配置文件：
> new compaction schedule module
> --
>
> Key: IOTDB-1604
> URL: https://issues.apache.org/jira/browse/IOTDB-1604
> Project: Apache IoTDB
> Issue Type: New Feature
>Reporter: Hai Liu
>Assignee: Liuxuxin
>Priority: Major
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png,
> 配置参数.zip
>
> Original Estimate: 16h
> Remaining Estimate: 16h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1604) new compaction schedule module
[ https://issues.apache.org/jira/browse/IOTDB-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17414664#comment-17414664 ] 刘珍 commented on IOTDB-1604: --- 20210914 new_compaction v3 commit 646a35093060cb67bb57183e7df2446434d50ca8 合并过程中error日志： !screenshot-2.png! > new compaction schedule module > -- > > Key: IOTDB-1604 > URL: https://issues.apache.org/jira/browse/IOTDB-1604 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Hai Liu >Assignee: Liuxuxin >Priority: Major > Attachments: screenshot-1.png, screenshot-2.png, 配置参数.zip > > Original Estimate: 48h > Remaining Estimate: 48h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1670) IOtimestamp_precision=ns ./sbin/start-cli.sh
刘珍 created IOTDB-1670: - Summary: IOtimestamp_precision=ns ./sbin/start-cli.sh Key: IOTDB-1670 URL: https://issues.apache.org/jira/browse/IOTDB-1670 Project: Apache IoTDB Issue Type: Bug Reporter: 刘珍 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1499) StorageGroupAlreadySetException raised when use IoTDBSink
闻乃松 created IOTDB-1499: -- Summary: StorageGroupAlreadySetException raised when use IoTDBSink Key: IOTDB-1499 URL: https://issues.apache.org/jira/browse/IOTDB-1499 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Flink Affects Versions: 0.12.0 Reporter: 闻乃松 Fix For: 0.12.2 Attachments: image-2021-07-14-10-07-13-462.png !image-2021-07-14-10-07-13-462.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1537) A user with INSERT_TIMESERIES permission failed to call session. insertTablet
刘珍 created IOTDB-1537: - Summary: A user with INSERT_TIMESERIES permission failed to call session. insertTablet Key: IOTDB-1537 URL: https://issues.apache.org/jira/browse/IOTDB-1537 Project: Apache IoTDB Issue Type: Bug Components: Server Affects Versions: 0.12.2-SNAPSHOT Reporter: 刘珍 Attachments: SessionExample.java rel/0.12 0728 88bc4289a61950cdb89c823b434931b280b98433 1. start-cli execute : CREATE USER test 'test' GRANT USER test PRIVILEGES 'SET_STORAGE_GROUP' on root.sg1 GRANT USER test PRIVILEGES 'CREATE_TIMESERIES' on root.sg1 GRANT USER test PRIVILEGES 'INSERT_TIMESERIES' on root.sg1 GRANT USER test PRIVILEGES 'READ_TIMESERIES' on root.sg1 GRANT USER test PRIVILEGES 'DELETE_TIMESERIES' on root.sg1 2. run SessionExample.java Exception in thread "main" org.apache.iotdb.rpc.StatementExecutionException: 602: No permissions for this operation BATCHINSERT at org.apache.iotdb.rpc.RpcUtils.verifySuccess(RpcUtils.java:86) at org.apache.iotdb.rpc.RpcUtils.verifySuccessWithRedirection(RpcUtils.java:92) at org.apache.iotdb.session.SessionConnection.insertTablet(SessionConnection.java:542) at org.apache.iotdb.session.Session.insertTablet(Session.java:1274) at SessionExample.insertTablet(SessionExample.java:135) at SessionExample.main(SessionExample.java:50) session.insertRecord is OK . -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1557) rel/0.12 : [Sync] mlog.bin sync failed
刘珍 created IOTDB-1557:
-
Summary: rel/0.12 : [Sync] mlog.bin sync failed
Key: IOTDB-1557
URL: https://issues.apache.org/jira/browse/IOTDB-1557
Project: Apache IoTDB
Issue Type: Bug
Components: Sync
Affects Versions: 0.12.2-SNAPSHOT
Reporter: 刘珍
Attachments: config.properties, image-2021-08-10-11-22-00-216.png
IoTDB :
rel/0.12 0809 75077fbfa62307e9cc0acdcd213d7b3c66f8ff27
sender & receiver conf/iotdb-env.sh :
MAX_HEAP_SIZE="20G"
MAX_DIRECT_MEMORY_SIZE=4G
1. benchmark generates data for sync
benchmark configuration file : See the attachment .
2. Start the receiver service
a. conf/iotdb-engine.properties
is_sync_enable=true
b. Start the receiver service
3. Start the sender sync service
a. conf/iotdb-sync-client.properties
server_ip=x.x.x.x
sync_period_in_second=60
b. ./tools/start-sync-client.sh
4. sender : log_sync.log
!image-2021-08-10-11-22-00-216.png|thumbnail!
2021-08-10 09:39:01,856 [pool-1-IoTDB-sync-client-timer-1] ERROR
o.a.i.d.s.s.t.SyncClient:433 - {color:#DE350B}Digest check of schema file
{color}/home/iotdb/liuzhen_test/rel_12/db_0806/data/system/schema/{color:#DE350B}mlog.bin
failed{color}, retry
2021-08-10 09:39:01,863 [pool-1-IoTDB-sync-client-timer-1] ERROR
o.a.i.d.s.s.t.SyncClient:224 - Sync failed
org.apache.iotdb.db.exception.SyncConnectionException: Can not sync schema
after 5 retries.
at
org.apache.iotdb.db.sync.sender.transfer.SyncClient.syncSchema(SyncClient.java:380)
at
org.apache.iotdb.db.sync.sender.transfer.SyncClient.syncAll(SyncClient.java:247)
at
org.apache.iotdb.db.sync.sender.transfer.SyncClient.lambda$startTimedTask$2(SyncClient.java:222)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1538) Use device template , create_schema to be true or false , the file size of "mlog. bin" is inconsistent
刘珍 created IOTDB-1538:
-
Summary: Use device template , create_schema to be true or false ,
the file size of "mlog. bin" is inconsistent
Key: IOTDB-1538
URL: https://issues.apache.org/jira/browse/IOTDB-1538
Project: Apache IoTDB
Issue Type: Bug
Components: Schema Manager
Affects Versions: master branch
Reporter: 刘珍
Attachments: SessionExample.java, config.properties.temp.45M
iotdb :
master 0723 72799f33215d5f6291544c354caf58c23a3dd04a
1. Create device template , set device templdate to 100 sg .
Run ExampleSession.java
2. Run benchmark
CREATE_SCHEMA=true , mlog.bin size is {color:#DE350B}*45M*{color}
CREATE_SCHEMA=false, mlog.bin size is {color:#DE350B}*90M*{color} , log_warn :
2021-07-26 04:11:35,488 [pool-8-IoTDB-RPC-Client-5] WARN
o.a.i.d.s.TSServiceImpl:2060 - Exception occurred while processing non-query.
org.apache.iotdb.db.exception.BatchProcessException: Batch process
failed:[TSStatus(code:300,
message:org.apache.iotdb.db.exception.metadata.PathAlreadyExistException: Path
[root.group_66.d_998666.s_20 ( which is incompatible with template )] already
exist), .
*Create schema or not mlog.bin should be the same size when using template*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1604) new compaction schedule module
[ https://issues.apache.org/jira/browse/IOTDB-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418968#comment-17418968 ] 刘珍 commented on IOTDB-1604: --- 2021-09-23 839ec9ae3920a52a063ed8edaa1ffc72e9d5f5d6 长测配置。 current task num超过max task num 2021-09-23 08:50:00,509 [pool-105-thread-1] INFO o.a.i.d.e.c.i.s.SizeTiredCompactionSelector:85 - root.group_19-0 [Compaction] SizeTiredCompactionSelector start to select, target file size is 2147483648, target file num is 50, *current task num is 12*, total task num is 9,* max task num is 10* 2021-09-23 08:50:00,509 [pool-57-thread-1] INFO o.a.i.d.e.c.i.s.SizeTiredCompactionSelector:85 - root.group_24-0 [Compaction] SizeTiredCompactionSelector start to select, target file size is 2147483648, target file num is 50, *current task num is 12*, total task num is 9, *max task num is 10* > new compaction schedule module > -- > > Key: IOTDB-1604 > URL: https://issues.apache.org/jira/browse/IOTDB-1604 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Hai Liu >Assignee: Liuxuxin >Priority: Major > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, > 配置参数.zip > > Original Estimate: 16h > Remaining Estimate: 16h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1729) [Benchmark]fix case of DB_SWITCH
张洪胤 created IOTDB-1729: -- Summary: [Benchmark]fix case of DB_SWITCH Key: IOTDB-1729 URL: https://issues.apache.org/jira/browse/IOTDB-1729 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 Ignore case of DB_SWITCH for use. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1826) [Benchmark] The write pressure improvement of IoTDB-Benchmark
[ https://issues.apache.org/jira/browse/IOTDB-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1826: -- Component/s: Benchmark Sprint: 2021-10 Assignee: 张洪胤 Description: During code refactoring, we need to consider the write pressure. Summary: [Benchmark] The write pressure improvement of IoTDB-Benchmark (was: [Benchmark] The improvement 藕粉IoTDB-Benchmark ) Remaining Estimate: 24h Original Estimate: 24h > [Benchmark] The write pressure improvement of IoTDB-Benchmark > - > > Key: IOTDB-1826 > URL: https://issues.apache.org/jira/browse/IOTDB-1826 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 24h > Remaining Estimate: 24h > > During code refactoring, we need to consider the write pressure. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1828) [Benchmark] The refactor of IoTDB-Benchmark
[ https://issues.apache.org/jira/browse/IOTDB-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1828: -- Assignee: 张洪胤 Description: Because of the possible of some future requirements, I think we need to refactor the architecture of IoTDB-Benchmark in the following way. # The abstraction of data schema. # The abstraction of data workload which provide data. # The abstraction of query workload which provide query. # The abstraction of client which do test. Also, I think the abstraction of query controller is a good idea Remaining Estimate: 48h (was: 24h) Original Estimate: 48h (was: 24h) > [Benchmark] The refactor of IoTDB-Benchmark > --- > > Key: IOTDB-1828 > URL: https://issues.apache.org/jira/browse/IOTDB-1828 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 48h > Remaining Estimate: 48h > > Because of the possible of some future requirements, I think we need to > refactor the architecture of IoTDB-Benchmark in the following way. > # The abstraction of data schema. > # The abstraction of data workload which provide data. > # The abstraction of query workload which provide query. > # The abstraction of client which do test. > Also, I think the abstraction of query controller is a good idea -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1827) [Benchmark] The ratio of out of order data in mode=1
张洪胤 created IOTDB-1827: -- Summary: [Benchmark] The ratio of out of order data in mode=1 Key: IOTDB-1827 URL: https://issues.apache.org/jira/browse/IOTDB-1827 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 Because of the rule of out-of-order data, we need to fix the generation of out-of-order data in benchmark -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1830) Run print-tsfile-resource-files.sh without passing parameters，the error message is incorrect
刘珍 created IOTDB-1830: - Summary: Run print-tsfile-resource-files.sh without passing parameters，the error message is incorrect Key: IOTDB-1830 URL: https://issues.apache.org/jira/browse/IOTDB-1830 Project: Apache IoTDB Issue Type: Bug Components: Tools/Others Affects Versions: 0.12.2 Reporter: 刘珍 Run print-tsfile-resource-files.sh without passing parameters，the error message is incorrect. print-tsfile-resource-files.sh should support parameter parsing. 此类工具应该支持参数解析。 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1829) When there are other files under the data directory，print-iotdb-data-dir.sh got IOException
刘珍 created IOTDB-1829:
-
Summary: When there are other files under the data
directory，print-iotdb-data-dir.sh got IOException
Key: IOTDB-1829
URL: https://issues.apache.org/jira/browse/IOTDB-1829
Project: Apache IoTDB
Issue Type: Bug
Components: Tools/Others
Affects Versions: 0.12.2
Reporter: 刘珍
Attachments: image-2021-10-13-11-14-44-791.png
rel/0.12 :
[root@i-7juoh9pu tsfileToolSet]# ls -l /data/iotdb_data/data/
total 4
-rw-r--r-- 1 root root0 Oct 13 11:04 {color:#DE350B}*a.txt*{color}
drwxr-xr-x 52 root root 4096 Sep 16 11:20 sequence
drwxr-xr-x 2 root root 10 Sep 16 11:20 unsequence
./print-iotdb-data-dir.sh /data/iotdb_data/data/
!image-2021-10-13-11-14-44-791.png!
有其他文件时，异常。实际上传入的参数/data/iotdb_data/data/下是有sequence and unsequence路径的。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1826) [Benchmark] The improvement 藕粉IoTDB-Benchmark
张洪胤 created IOTDB-1826: -- Summary: [Benchmark] The improvement 藕粉IoTDB-Benchmark Key: IOTDB-1826 URL: https://issues.apache.org/jira/browse/IOTDB-1826 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1828) [Benchmark] The refactor of IoTDB-Benchmark
张洪胤 created IOTDB-1828: -- Summary: [Benchmark] The refactor of IoTDB-Benchmark Key: IOTDB-1828 URL: https://issues.apache.org/jira/browse/IOTDB-1828 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1836) Execute time range query : Msg: 500: [INTERNAL_SERVER_ERROR]
刘珍 created IOTDB-1836:
-
Summary: Execute time range query : Msg: 500:
[INTERNAL_SERVER_ERROR]
Key: IOTDB-1836
URL: https://issues.apache.org/jira/browse/IOTDB-1836
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Affects Versions: 0.12.2
Reporter: 刘珍
Attachments: config.properties, iotdb-engine.properties,
iotdb_log.tar.gz, tracing.txt
rel/0.12 24cc07dffdaf79fda8290c24e8329e20a53015df
Exception message:
Msg: 500: [INTERNAL_SERVER_ERROR] Exception occurred while executing
"{color:#DE350B}SELECT s_0 FROM root.test.g_15.d_2890 WHERE time >=
153737786 AND time <= 1537377865000{color}". null
Reproduce steps :
1. iotdb-engine.properties
compaction_strategy=NO_COMPACTION
enable_unseq_compaction=false
enable_last_cache=false
enable_wal=false
max_deduplicated_path_num=1
query_timeout_threshold=6000
2. Start iotdb
3. Run benchmark （See attachment config.properties for configuration parameters）
cd ${benchmark_dir}
# First test 第1轮测试（读写混合/乱序）
./benchmark.sh > 1013_1.out
sleep 2s
# 删除所有存储组
${iotdb_dir}/sbin/start-cli.sh -e "delete storage group root.*"
sleep 2s
# show.out 结果显示存储组全部删除成功
${iotdb_dir}/sbin/start-cli.sh -e "show storage group" > show.out
sleep 2s
mv data data_1
# Second test 第2轮测试（读写混合/乱序），bm配置同第1轮测试
./benchmark.sh > 1013_2.out
{color:#DE350B}*第2轮测试，查询报错*{color}(1013_2.out )：
2021-10-13 15:54:25,978 ERROR
cn.edu.tsinghua.iotdb.benchmark.iotdb012.IoTDB:608 - exception occurred when
execute query=SELECT s_0 FROM root.test.g_5.d_930 WHERE time >= 1537377805000
AND time <= 153737781
org.apache.iotdb.jdbc.IoTDBSQLException: 500: [INTERNAL_SERVER_ERROR] Exception
occurred while executing executeQueryStatement. null
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1824) print-iotdb-data-dir.sh should support “--help”
刘珍 created IOTDB-1824:
-
Summary: print-iotdb-data-dir.sh should support “--help”
Key: IOTDB-1824
URL: https://issues.apache.org/jira/browse/IOTDB-1824
Project: Apache IoTDB
Issue Type: Improvement
Components: Tools/Others
Reporter: 刘珍
$iotdb_dir/tools/tsfileToolSet
print-iotdb-data-dir.sh {color:#DE350B}*--help*{color}
print-tsfile-resource-files.sh
print-tsfile-sketch.sh
should support --help to see how to use it
这3个工具应该支持--help，否则不知道使用方法。
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1820) [Docker]Enhance of Grafana part
张洪胤 created IOTDB-1820: -- Summary: [Docker]Enhance of Grafana part Key: IOTDB-1820 URL: https://issues.apache.org/jira/browse/IOTDB-1820 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Assignee: 张洪胤 Fix For: master branch I find there are some inconvenience when use grafana to show data in iotdb. I think docker can be a good solution. I will fix this problem in following parts. # I will edit /iotdb/grafana to support the change of ip and port in properties file. # Support the deployment of iotdb, grafana and grafana-connector by docker compose. # Fix the doc related to all above. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1866) [Benchmark] Expanding read-write mixed scenarios
张洪胤 created IOTDB-1866: -- Summary: [Benchmark] Expanding read-write mixed scenarios Key: IOTDB-1866 URL: https://issues.apache.org/jira/browse/IOTDB-1866 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 Because of the requirements, benchmark need to support query recent data in read-write mixed scenarios. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1867) [Benchmark] Error when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x
张洪胤 created IOTDB-1867: -- Summary: [Benchmark] Error when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x Key: IOTDB-1867 URL: https://issues.apache.org/jira/browse/IOTDB-1867 Project: Apache IoTDB Issue Type: Bug Components: Benchmark Reporter: 张洪胤 Assignee: 张洪胤 Error happens when set OPERATION_PROPORTION=1:x:x:x:x:x:x:x:x:x:x, benchmark will only write and not query -- This message was sent by Atlassian Jira (v8.3.4#803005)
