[jira] [Created] (IOTDB-6348) Cannot query the updated value
Yuan Tian created IOTDB-6348: Summary: Cannot query the updated value Key: IOTDB-6348 URL: https://issues.apache.org/jira/browse/IOTDB-6348 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian change avg_series_point_number_threshold=2 and then execute the following sql: ``` create timeseries root.db.d1.s1 with datatype=INT32,encoding=PLAIN; insert into root.db.d1(time,s1) values (2,2); insert into root.db.d1(time,s1) values (3,3); insert into root.db.d1(time,s1) values (2,20); insert into root.db.d1(time,s1) values (5,5); insert into root.db.d1(time,s1) values (6,6); insert into root.db.d1(time,s1) values (5,50); SELECT s1 FROM root.db.d1 where time = 5; ``` we will get the value 5, not 50. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6347) Support more info in explain analyze verbose
Yuan Tian created IOTDB-6347: Summary: Support more info in explain analyze verbose Key: IOTDB-6347 URL: https://issues.apache.org/jira/browse/IOTDB-6347 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: yang caiyin h2. new metrics # the cost to dispatch FragmentInstance for one query # pageReaderMaxUsedMemorySize for one FragmentInstance # TimeSeriesMetadataModificationCount/Time for one FragmentInstance h2. bug fixed # Fix wrong filteredRowCount in FilterAndTransformOperator # Fix permission of EXPLAIN ANALYZE to keep it the same query SQL. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6346) Show devices doesn't take ttl into account
Yuan Tian created IOTDB-6346: Summary: Show devices doesn't take ttl into account Key: IOTDB-6346 URL: https://issues.apache.org/jira/browse/IOTDB-6346 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: yang caiyin Currently, we support show devices where timeCondition, but while executing that query, we don't take ttl into account which means that some devices' data should be filtered by ttl but still exist in result set. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6344) Don't display null in cli
Yuan Tian created IOTDB-6344: Summary: Don't display null in cli Key: IOTDB-6344 URL: https://issues.apache.org/jira/browse/IOTDB-6344 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2024-06-26-14-40-02-441.png execute the following sql: ``` CREATE DATABASE root.sg_type; CREATE TIMESERIES root.sg_type.d_0.s_boolean BOOLEAN; CREATE TIMESERIES root.sg_type.d_0.s_int32 INT32; CREATE TIMESERIES root.sg_type.d_0.s_int64 INT64; CREATE TIMESERIES root.sg_type.d_0.s_float FLOAT; CREATE TIMESERIES root.sg_type.d_0.s_double DOUBLE; CREATE TIMESERIES root.sg_type.d_0.s_text TEXT; CREATE TIMESERIES root.sg_type.d_0.s_timestamp TIMESTAMP; CREATE TIMESERIES root.sg_type.d_0.s_date DATE; CREATE TIMESERIES root.sg_type.d_0.s_blob BLOB; CREATE TIMESERIES root.sg_type.d_0.s_string STRING; INSERT INTO root.sg_type.d_0(time, s_int32, s_int64, s_float, s_double, s_text) VALUES (0, 0, 0, 0.00, 0.00, 'text0'); ``` we don't insert s_boolean, so we should get null, but we still get false !image-2024-06-26-14-40-02-441.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6342) FragmentInstanceContext'size won't decrease to 0
Yuan Tian created IOTDB-6342: Summary: FragmentInstanceContext'size won't decrease to 0 Key: IOTDB-6342 URL: https://issues.apache.org/jira/browse/IOTDB-6342 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian To replay, you can refer to https://issues.apache.org/jira/browse/IOTDB-6340. Then you can see the fragment instance context size won't decrease to 0 in metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6341) MemoryPool's query memory reservation size don't decrease to 0
Yuan Tian created IOTDB-6341: Summary: MemoryPool's query memory reservation size don't decrease to 0 Key: IOTDB-6341 URL: https://issues.apache.org/jira/browse/IOTDB-6341 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu Attachments: image-2024-06-19-11-09-45-812.png The replay method is same as https://issues.apache.org/jira/browse/IOTDB-6340. We need 3C3D and then, session should connect to the DN that doesn't contains that device's data. Then you can see MemoryPool's query memory reservation size won't decrease to 0 !image-2024-06-19-11-09-45-812.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6340) Show queries can see failed queries
[
https://issues.apache.org/jira/browse/IOTDB-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuan Tian reassigned IOTDB-6340:
Attachment: image-2024-06-19-11-02-08-832.png
Component/s: Core/Query
Assignee: Yuan Tian
Description:
timeout is 60s, but while executing show queries, we can still see some queries
!image-2024-06-19-11-02-08-832.png!
These queries are all throw query memory not enough excepton and should clear
them.
However if user don't don't close the session or JDBCStatement, they won't be
cleared any more.
To replay, we can give DN 1G memory and create an aligned device with 10
sensor, then using session.executeQueryStatement("Select last * from
root.db.d1"), then don't close session.
Summary: Show queries can see failed queries (was: Show)
> Show queries can see failed queries
> ---
>
> Key: IOTDB-6340
> URL: https://issues.apache.org/jira/browse/IOTDB-6340
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Query
>Reporter: Yuan Tian
>Assignee: Yuan Tian
>Priority: Major
> Attachments: image-2024-06-19-11-02-08-832.png
>
>
> timeout is 60s, but while executing show queries, we can still see some
> queries
> !image-2024-06-19-11-02-08-832.png!
> These queries are all throw query memory not enough excepton and should clear
> them.
> However if user don't don't close the session or JDBCStatement, they won't be
> cleared any more.
>
> To replay, we can give DN 1G memory and create an aligned device with 10
> sensor, then using session.executeQueryStatement("Select last * from
> root.db.d1"), then don't close session.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6340) Show
Yuan Tian created IOTDB-6340: Summary: Show Key: IOTDB-6340 URL: https://issues.apache.org/jira/browse/IOTDB-6340 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6339) Optimize the time slice control of SeriesScanOperator and AlignedSeriesScanOperator
Yuan Tian created IOTDB-6339: Summary: Optimize the time slice control of SeriesScanOperator and AlignedSeriesScanOperator Key: IOTDB-6339 URL: https://issues.apache.org/jira/browse/IOTDB-6339 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian more details can be seen in https://timechor.feishu.cn/docx/IMHxdHhrRoPg88x69wTc4RqynFf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6338) Wrong query result while using some value filter + limit
[ https://issues.apache.org/jira/browse/IOTDB-6338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-6338: Assignee: Minghui Liu > Wrong query result while using some value filter + limit > > > Key: IOTDB-6338 > URL: https://issues.apache.org/jira/browse/IOTDB-6338 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Query >Reporter: Yuan Tian >Assignee: Minghui Liu >Priority: Major > Attachments: image-2024-06-07-16-00-07-249.png > > > To replay, using the following sqls: > ``` > insert into root.db.d1(time, s1, s2) aligned values(now(), 1, 1); > insert into root.db.d1(time, s1, s2) aligned values(now(), 2, 2); > insert into root.db.d1(time, s1, s2) aligned values(now(), 3, 3); > insert into root.db.d1(time, s1, s2) aligned values(now(), 4, 40); > insert into root.db.d1(time, s1, s2) aligned values(now(), 5, 50); > insert into root.db.d1(time, s1, s2) aligned values(now(), 6, 60); > select s1, s2 from root.db.d1 where s1 != s2 limit 1; > ``` > > we expect to get the line `4, 40`, but in current version, we got empty > result set which is wrong. > !image-2024-06-07-16-00-07-249.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6338) Wrong query result while using some value filter + limit
Yuan Tian created IOTDB-6338: Summary: Wrong query result while using some value filter + limit Key: IOTDB-6338 URL: https://issues.apache.org/jira/browse/IOTDB-6338 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Attachments: image-2024-06-07-16-00-07-249.png To replay, using the following sqls: ``` insert into root.db.d1(time, s1, s2) aligned values(now(), 1, 1); insert into root.db.d1(time, s1, s2) aligned values(now(), 2, 2); insert into root.db.d1(time, s1, s2) aligned values(now(), 3, 3); insert into root.db.d1(time, s1, s2) aligned values(now(), 4, 40); insert into root.db.d1(time, s1, s2) aligned values(now(), 5, 50); insert into root.db.d1(time, s1, s2) aligned values(now(), 6, 60); select s1, s2 from root.db.d1 where s1 != s2 limit 1; ``` we expect to get the line `4, 40`, but in current version, we got empty result set which is wrong. !image-2024-06-07-16-00-07-249.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6336) Add configuration to control max retry count and whether to rety for unknown errors
Yuan Tian created IOTDB-6336: Summary: Add configuration to control max retry count and whether to rety for unknown errors Key: IOTDB-6336 URL: https://issues.apache.org/jira/browse/IOTDB-6336 Project: Apache IoTDB Issue Type: New Feature Components: Core/Engine Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2024-06-03-11-04-09-651.png Now when encountering dispatch error while sending write request to a remote datanode, we will retry while receiving the following TSStatusCode !image-2024-06-03-11-04-09-651.png! However, for some unknown errors like 301 and 305, we may not need to retry for it in some case. And the max retry count is always 10(hard code), this number should also be changable in configuration file. And we want both the above two new added confiugration can be hot loaded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6327) Random choosing available nodes to send sql requests
Yuan Tian created IOTDB-6327: Summary: Random choosing available nodes to send sql requests Key: IOTDB-6327 URL: https://issues.apache.org/jira/browse/IOTDB-6327 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Now even if we construct session with only one node url, session will automatically fetch all available node urls in the cluster. However, when we use `executeQueryStatement`, we can only send the sql query to the first node url ( we can see that in the metrics panel that only one DN has query OPS) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6326) Column Headers of auth statement is unstandard
Yuan Tian created IOTDB-6326: Summary: Column Headers of auth statement is unstandard Key: IOTDB-6326 URL: https://issues.apache.org/jira/browse/IOTDB-6326 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2024-05-08-12-00-49-693.png ColumnHeaders of list privileges of user/role and list user/role are not standard: !image-2024-05-08-12-00-49-693.png! We expect them to be like: User, Role, Path, Privileges, GrantOption -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6322) Let show variables can be executed by anyone
Yuan Tian created IOTDB-6322: Summary: Let show variables can be executed by anyone Key: IOTDB-6322 URL: https://issues.apache.org/jira/browse/IOTDB-6322 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Previously, we need MAINTAIN auth to execute `show variables`, now we want to every user can execute this command without any auth. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6316) Concurrent bug between load and compaction
Yuan Tian created IOTDB-6316: Summary: Concurrent bug between load and compaction Key: IOTDB-6316 URL: https://issues.apache.org/jira/browse/IOTDB-6316 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: Yuan Tian Assignee: Yuan Tian The case is that we may get a tsfile resource without tsfile in disk which is caused by concurrent bug between compaction and load. More details about the lock analysis can be seen in https://apache-iotdb.feishu.cn/docx/RrBrdXHPgoJTcxxoPxMc8eNXndd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6315) Add Metric for resource index memory usage and degraded num
Yuan Tian created IOTDB-6315: Summary: Add Metric for resource index memory usage and degraded num Key: IOTDB-6315 URL: https://issues.apache.org/jira/browse/IOTDB-6315 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian We need to add total resource number, degraded resource number, max index memory size and used index memory size metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6313) Correct the implementation of FILL(LINEAR)
Yuan Tian created IOTDB-6313: Summary: Correct the implementation of FILL(LINEAR) Key: IOTDB-6313 URL: https://issues.apache.org/jira/browse/IOTDB-6313 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian more details can be seen in https://apache-iotdb.feishu.cn/docx/OlrNd4oSmos8QVxCGm2cxThanBg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6312) Print correct error msg while using wrong password in session
Yuan Tian created IOTDB-6312: Summary: Print correct error msg while using wrong password in session Key: IOTDB-6312 URL: https://issues.apache.org/jira/browse/IOTDB-6312 Project: Apache IoTDB Issue Type: Improvement Components: Client/Java Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2024-03-18-14-17-11-463.png If we write a wrong password in Session, we now get an error msg like the following: !image-2024-03-18-14-17-11-463.png! It never tells us that we write a wrong password. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6310) Optimize for query resource init
Yuan Tian created IOTDB-6310: Summary: Optimize for query resource init Key: IOTDB-6310 URL: https://issues.apache.org/jira/browse/IOTDB-6310 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian we use timefilter to filter useless timepartition instead of getting all of them and then filter tsfile in them one by one. We insert `0~` points whose timestamp is also `0~` and execute `flush` after each point insert and then insert one point with timestamp now(). As so, we will get two partitions, one contains 10,000 tsfiles, another one contains only one tsfile. execute the following sql: (only the last tsfile satisfies) ``` select s1 from root.db.d1 where time > now() - 1h; ``` before opt, the time for query init tsfile list are:(about 2.5ms) ``` 3057000 2356292 3258834 2415417 2876041 2395750 2564833 ``` after opt, the time for query init tsfile list are:(about 0.047 ms) ``` 47500 39792 33875 31958 37584 5 45709 ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6305) Get current timestamp of iotdb server
Yuan Tian created IOTDB-6305: Summary: Get current timestamp of iotdb server Key: IOTDB-6305 URL: https://issues.apache.org/jira/browse/IOTDB-6305 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuxin Zhang We want to get the current timestamp of IoTDB server through sql, like the following: ``` SHOW CURRENT_TIMESTAMP; ``` The result will be one row and one column, like: - current_timestamp - 1709256258000 - This time is the time from server that you directly connect to, so you may find this time may be different from other nodes in you IoTDB cluster if you don't do the synchronization and calibration of computer clocks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6300) Support time column at any column in insert sql
Yuan Tian created IOTDB-6300:
Summary: Support time column at any column in insert sql
Key: IOTDB-6300
URL: https://issues.apache.org/jira/browse/IOTDB-6300
Project: Apache IoTDB
Issue Type: New Feature
Components: Core/Query
Reporter: Yuan Tian
Assignee: Yuan Tian
Now we only support time column at the first column of insert sql, like:
{code:java}
insert into root.db.d1(time,s1,s2) values(1,2,3); {code}
And we don't support `` to include the `time`, if we do so, we will get an
error:
{code:java}
insert into root.db.d1(`time`,s1,s2) values(1,2,3); {code}
So we want to support the following two cases:
1. time column can be placed at any index of the column list:
{code:java}
insert into root.db.d1(s1,s2,time) values(1,2,3); {code}
2. we can add `` in time column:
{code:java}
insert into root.db.d1(`time`,s1,s2) values(1,2,3); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6298) group by time interval bug while using number larger than INTEGER.MAX_VALUE
Yuan Tian created IOTDB-6298: Summary: group by time interval bug while using number larger than INTEGER.MAX_VALUE Key: IOTDB-6298 URL: https://issues.apache.org/jira/browse/IOTDB-6298 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Change the timestamp_precision=ns. The following query should only return 1 row, but it doesn't: ``` insert into root.db.d1(time,s1) values(0,0) select count(s1) from root.db.d1 group by([0, 100), 100ns) ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6296) Memory leak in MQTTService
Yuan Tian created IOTDB-6296: Summary: Memory leak in MQTTService Key: IOTDB-6296 URL: https://issues.apache.org/jira/browse/IOTDB-6296 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2024-02-19-18-12-29-624.png After a long time running, we will get the following error msg. However, if we restart the IoTDB, it will recover. !image-2024-02-19-18-12-13-835.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6294) Can't use placeholder in INTO clause while using group by level
Yuan Tian created IOTDB-6294:
Summary: Can't use placeholder in INTO clause while using group by
level
Key: IOTDB-6294
URL: https://issues.apache.org/jira/browse/IOTDB-6294
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: Yuan Tian
Assignee: Minghui Liu
Attachments: image-2024-01-19-15-43-12-316.png
We can successfully create CQ in 0.13.X using the following sql, but we cannot
succeed to do that in 1.X
```
CREATE CONTINUOUS QUERY cq_group_event_online_status_1m RESAMPLE EVERY 1m FOR
1m BOUNDARY 2024-01-19T14:00:00.000+08:00 BEGIN select sum(status) INTO
[root.test.event.PH|http://root.test.event.ph/].${4}.${5}.${6}.status_sum_1m
from root.test.event.*.*.*.* group by time(1m), level=4,5,6 END;
```
!image-2024-01-19-15-43-12-316.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-6279) Query module exceptionally shows out of memory
[ https://issues.apache.org/jira/browse/IOTDB-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-6279: Assignee: liaolanyu > Query module exceptionally shows out of memory > -- > > Key: IOTDB-6279 > URL: https://issues.apache.org/jira/browse/IOTDB-6279 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Sicheng Yu >Assignee: liaolanyu >Priority: Major > Attachments: car.zip > > > 问题： > data 文件夹大小一共 55 MB 左右，启动 datanode 的 jvm 有 2G，执行查询 select count( * ) from > root.** group by level=1,2 一直显示内存不足，iotdb-common.properties 中配置了 > datanode_memory_proportion=3:10:1:1:1:1，enable_mem_control=false > 复现步骤： > 1. 执行语句 load 'path/to/dataset' onSuccess=none > 2. 执行查询 select count( * ) from root.** group by level=1,2 > 3. 显示：Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 301: Query is aborted > since it requests more memory than can be allocated. > Problem: > The size of the data folder is about 55 MB, and the jvm that starts datanode > is 2G, but the query select count( * ) from root.** group by level=1,2 keeps > showing out of memory. > Steps to reproduce: > 1. execute the statement load 'path/to/dataset' onSuccess=none > 2. Execute the query select count( * ) from root.** group by level=1,2 > 3. show: Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 301: Query is aborted > since it requests more memory than can be allocated. > ERROR Logs： > 136028 [Query-Worker-Thread-11$20231226_040029_00044_1.1.0.3] INFO > o.a.i.d.s.b.TimeSeriesMetadataCache - TimeSeriesMetadataCache size = > 454669257 > 136031 [Query-Worker-Thread-1$20231226_040029_00044_1.1.0.7] INFO > o.a.i.d.s.buffer.BloomFilterCache - BloomFilterCache size = 2273346 > 136113 [Query-Worker-Thread-0$20231226_040029_00044_1.1.0.6] WARN > o.a.i.d.q.e.memory.MemoryPool - Cannot reserve 334626(Max: 123016) bytes > memory from MemoryPool for planNodeId1321-5 > 136113 [Query-Worker-Thread-0$20231226_040029_00044_1.1.0.6] WARN > o.a.i.d.q.e.s.AbstractDriverThread - [ExecuteFailed] > java.lang.RuntimeException: java.lang.IllegalArgumentException: Query is > aborted since it requests more memory than can be allocated. > at > org.apache.iotdb.db.queryengine.execution.driver.Driver.processInternal(Driver.java:249) > at > org.apache.iotdb.db.queryengine.execution.driver.Driver.lambda$processFor$1(Driver.java:150) > at > org.apache.iotdb.db.queryengine.execution.driver.Driver.tryWithLock(Driver.java:326) > at > org.apache.iotdb.db.queryengine.execution.driver.Driver.processFor(Driver.java:131) > at > org.apache.iotdb.db.queryengine.execution.schedule.DriverTaskThread.execute(DriverTaskThread.java:83) > at > org.apache.iotdb.db.queryengine.execution.schedule.AbstractDriverThread.run(AbstractDriverThread.java:73) > Caused by: java.lang.IllegalArgumentException: Query is aborted since it > requests more memory than can be allocated. > at > org.apache.iotdb.db.queryengine.execution.memory.MemoryPool.reserve(MemoryPool.java:239) > at > org.apache.iotdb.db.queryengine.execution.exchange.SharedTsBlockQueue.add(SharedTsBlockQueue.java:225) > at > org.apache.iotdb.db.queryengine.execution.exchange.sink.LocalSinkChannel.send(LocalSinkChannel.java:148) > at > org.apache.iotdb.db.queryengine.execution.driver.Driver.processInternal(Driver.java:241) > ... 5 common frames omitted > 136123 [Query-Worker-Thread-0$20231226_040029_00044_1.1.0.6] WARN > o.a.i.d.q.e.s.DriverScheduler - The task 20231226_040029_00044_1.1.0.6 is > aborted. All other tasks in the same query will be cancelled > 136444 [pool-27-IoTDB-ClientRPC-Processor-1$20231226_040029_00044_1] WARN > o.a.i.d.q.p.e.QueryExecution - [ResultHandleAborted] > 136444 [pool-27-IoTDB-ClientRPC-Processor-1] WARN > o.a.i.db.utils.ErrorHandlingUtils - Status code: 301, Query Statement: > "select count(*) from root.** group by level=1,2". executeStatement failed > org.apache.iotdb.commons.exception.IoTDBException: > org.apache.iotdb.commons.exception.IoTDBException: Query is aborted since it > requests more memory than can be allocated. > at > org.apache.iotdb.db.queryengine.plan.execution.QueryExecution.dealWithException(QueryExecution.java:547) > at > org.apache.iotdb.db.queryengine.plan.execution.QueryExecution.getResult(QueryExecution.java:535) > at > org.apache.iotdb.db.queryengine.plan.execution.QueryExecution.getByteBufferBatchResult(QueryExecution.java:565) > at > org.apache.iotdb.db.utils.QueryDataSetUtils.convertQueryResultByFetchSize(QueryDataSetUtils.java:604) > at > org.apache.iotdb.db.protocol.thrift.impl.ClientRPCServiceImpl.lambda$static$0(ClientRPCServiceImpl.java:245) > at >
[jira] [Created] (IOTDB-6275) limit shouldn't be push down while having order by
Yuan Tian created IOTDB-6275: Summary: limit shouldn't be push down while having order by Key: IOTDB-6275 URL: https://issues.apache.org/jira/browse/IOTDB-6275 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Minghui Liu Attachments: image-2023-12-21-21-01-27-180.png We cannot push limit down to scan if we have order by clause. ``` insert into root.db.d1(time,s1,s2) aligned values(now(),1,1) explain select * from root.db.d1 order by s1 limit 10; ``` !image-2023-12-21-21-01-27-180.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6272) Create timeseries root.db.`0e38`.s1 failed
Yuan Tian created IOTDB-6272: Summary: Create timeseries root.db.`0e38`.s1 failed Key: IOTDB-6272 URL: https://issues.apache.org/jira/browse/IOTDB-6272 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu In an empty database, we cannot create timeseries root.db.`0e38`.s1 ``` create timeseries root.sg.`0e38`.s1 ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6269) Ignore the data whose datatype doesn't match with SchemaRegion
Yuan Tian created IOTDB-6269: Summary: Ignore the data whose datatype doesn't match with SchemaRegion Key: IOTDB-6269 URL: https://issues.apache.org/jira/browse/IOTDB-6269 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Now delete has concurrent bug which may cause some tsfile may not be deleted(the reason can be seen in [https://apache-iotdb.feishu.cn/docx/FBqwd8562of2BJxDnQUcu3tRnsW], and we are trying to fix it but it may take some time), in such case, if we insert the same name sensor with different data type, while querying, it will throw excption: !https://private-user-images.githubusercontent.com/16079446/286929089-763c3ebc-dc2d-4b4d-ba60-f7f8dc0a14c2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTEiLCJleHAiOjE3MDI5NzYyNzAsIm5iZiI6MTcwMjk3NTk3MCwicGF0aCI6Ii8xNjA3OTQ0Ni8yODY5MjkwODktNzYzYzNlYmMtZGMyZC00YjRkLWJhNjAtZjdmOGRjMGExNGMyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFJV05KWUFYNENTVkVINTNBJTJGMjAyMzEyMTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjMxMjE5VDA4NTI1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZjNjEyN2YwMTIyNjljNDA5YTg1MjA0OWI2ZTE3YzlmZjk5ZTQ0ODI3YTE2MjUwYmNlMWEyMTg0OWYyNjkxOGEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.ffpOtyvxYQFG37xodhTLWBcQ2Y38Fpc26eQX0IGDf30! Actually, we can simply ignore these data while processing query instead of throw exception. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6265) Construct SessionPool using empty nodeUrls should throw exception
Yuan Tian created IOTDB-6265: Summary: Construct SessionPool using empty nodeUrls should throw exception Key: IOTDB-6265 URL: https://issues.apache.org/jira/browse/IOTDB-6265 Project: Apache IoTDB Issue Type: Bug Components: Client/Java Reporter: Yuan Tian Assignee: Yuan Tian while we use an empty nodeUrls to construct SessionPool, we will succeed(using localhost and 6667 as default host and port) which is not we want. We expect it throw exception to tell us that nodeUrls shouldn't be empty. ``` SessionPool sessionPool = new SessionPool(Collections.emptyList(), "root", "root", 3); ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6254) Missing some data points while using limit in aligned sensor cases
Yuan Tian created IOTDB-6254: Summary: Missing some data points while using limit in aligned sensor cases Key: IOTDB-6254 URL: https://issues.apache.org/jira/browse/IOTDB-6254 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian using the following sqls, you can replay the case: ``` insert into root.db.d1(time,s1,s2) aligned values(1,1,1); insert into root.db.d1(time,s1,s2) aligned values(2,2,2); insert into root.db.d1(time,s1,s2) aligned values(3,3,3); insert into root.db.d1(time,s1,s2) aligned values(4,4,4); flush; ``` if you execute `select s1 from root.db.d1 where time >= 3 limit 2;`, you will get empty result. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6242) Specify which datanode doesn't have udf jar
[ https://issues.apache.org/jira/browse/IOTDB-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-6242: Assignee: Zhihao Shen > Specify which datanode doesn't have udf jar > --- > > Key: IOTDB-6242 > URL: https://issues.apache.org/jira/browse/IOTDB-6242 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Query >Reporter: Yuan Tian >Assignee: Zhihao Shen >Priority: Major > Attachments: image-2023-11-08-15-21-24-751.png > > > In cluster mode, if we need to create udf without specifying uri, we need to > make sure that each datanode has the jar in ext/udf, if not so, currently, we > will throw exception like following: > !image-2023-11-08-15-21-24-751.png! > > To be more user-friendly, we need to make the error msg more readable and > tell users which datanodes miss the udf jar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6243) Supporr time duration thredshold in fill(PREVIOUS) clause
Yuan Tian created IOTDB-6243: Summary: Supporr time duration thredshold in fill(PREVIOUS) clause Key: IOTDB-6243 URL: https://issues.apache.org/jira/browse/IOTDB-6243 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Currently, we fill any null value if there is an non-null value in the previous while we use fill(previous), however in some cases we want the null value keep null if the time duration between current value and previous non-null value exceed some specified thredshold. More details can been seen in https://apache-iotdb.feishu.cn/docx/M3RUdL3nGoKRbSxPmnscR9LJnGd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6242) Specify which datanode doesn't have udf jar
[ https://issues.apache.org/jira/browse/IOTDB-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-6242: Assignee: (was: Yuan Tian) > Specify which datanode doesn't have udf jar > --- > > Key: IOTDB-6242 > URL: https://issues.apache.org/jira/browse/IOTDB-6242 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Query >Reporter: Yuan Tian >Priority: Major > Attachments: image-2023-11-08-15-21-24-751.png > > > In cluster mode, if we need to create udf without specifying uri, we need to > make sure that each datanode has the jar in ext/udf, if not so, currently, we > will throw exception like following: > !image-2023-11-08-15-21-24-751.png! > > To be more user-friendly, we need to make the error msg more readable and > tell users which datanodes miss the udf jar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6242) Specify which datanode doesn't have udf jar
Yuan Tian created IOTDB-6242: Summary: Specify which datanode doesn't have udf jar Key: IOTDB-6242 URL: https://issues.apache.org/jira/browse/IOTDB-6242 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2023-11-08-15-21-24-751.png In cluster mode, if we need to create udf without specifying uri, we need to make sure that each datanode has the jar in ext/udf, if not so, currently, we will throw exception like following: !image-2023-11-08-15-21-24-751.png! To be more user-friendly, we need to make the error msg more readable and tell users which datanodes miss the udf jar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6237) Improve the process of query execution
Yuan Tian created IOTDB-6237: Summary: Improve the process of query execution Key: IOTDB-6237 URL: https://issues.apache.org/jira/browse/IOTDB-6237 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6230) Add HEAPDUMP configuration in datanode-env.sh
Yuan Tian created IOTDB-6230:
Summary: Add HEAPDUMP configuration in datanode-env.sh
Key: IOTDB-6230
URL: https://issues.apache.org/jira/browse/IOTDB-6230
Project: Apache IoTDB
Issue Type: Improvement
Reporter: Yuan Tian
Assignee: Yuan Tian
add HeapDump configuration in datanode-env to let DBA can quickly add
{{{}-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath={}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6229) Add java doc in SessionDataSet to guide user use DataIterator
Yuan Tian created IOTDB-6229: Summary: Add java doc in SessionDataSet to guide user use DataIterator Key: IOTDB-6229 URL: https://issues.apache.org/jira/browse/IOTDB-6229 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian add java doc for SessionDataSet.next(), and recommend users to use SessionDataSet.DataIterator to iterate their result set if possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6228) Improve the high availability of IoTDB
Yuan Tian created IOTDB-6228: Summary: Improve the high availability of IoTDB Key: IOTDB-6228 URL: https://issues.apache.org/jira/browse/IOTDB-6228 Project: Apache IoTDB Issue Type: Improvement Components: Core/Engine Reporter: Yuan Tian Assignee: Yuan Tian For 3C3D 2 replicas or 3 replicas dataregion, if we kill one datanode, client should keep inserting data successfully without any error. However, currently, there is no retry logic in dispatch for write, so if the leader of one DataRegionGroup is down, the dispatch phase will fail and will return a 302 status code to Session, and meet this kind of StatusCode, Session won't retry this write request, it will throw this exception to the upper layer. You will get the error msg like the following: !https://user-images.githubusercontent.com/16079446/277609629-c0987905-5816-4daa-a664-0503c0edac12.png! more details about this improvement can be found in this feishu doc([https://timechor.feishu.cn/docx/WuVJdNpGOowEGIxvaOlcwt9mngg]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6225) Support bacth process interface in UDF api
Yuan Tian created IOTDB-6225: Summary: Support bacth process interface in UDF api Key: IOTDB-6225 URL: https://issues.apache.org/jira/browse/IOTDB-6225 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian We need to support bacth process interface in UDF api which can directly process TsBlock instead of converting TsBlock to RowRecord row by row. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6215) Change the hint msg while memory it enough to create more timeseries
Yuan Tian created IOTDB-6215: Summary: Change the hint msg while memory it enough to create more timeseries Key: IOTDB-6215 URL: https://issues.apache.org/jira/browse/IOTDB-6215 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian Previous error msg is: There are too many timeseries in memory. Current memory usage is %s and series num is %s. Please increase MAX_HEAP_SIZE in datanode-env.sh/bat, restart and create timeseries again. We want to guide users to use device template, so we change it to: Too many timeseries in memory without device template(current memory: %s, series num: %s). To optimize memory, DEVICE TEMPLATE is more recommended when devices have same time series. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6212) Change the hint msg while memory it enough to create more timeseries
Yuan Tian created IOTDB-6212: Summary: Change the hint msg while memory it enough to create more timeseries Key: IOTDB-6212 URL: https://issues.apache.org/jira/browse/IOTDB-6212 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian Previous error msg is: There are too many timeseries in memory. Current memory usage is %s and series num is %s. Please increase MAX_HEAP_SIZE in datanode-env.sh/bat, restart and create timeseries again. We want to guide users to use device template, so we change it to: Too many timeseries in memory without device template(current memory: %s, series num: %s). To optimize memory, DEVICE TEMPLATE is more recommended when devices have same time series. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6214) Change the hint msg while memory it enough to create more timeseries
Yuan Tian created IOTDB-6214: Summary: Change the hint msg while memory it enough to create more timeseries Key: IOTDB-6214 URL: https://issues.apache.org/jira/browse/IOTDB-6214 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian Previous error msg is: There are too many timeseries in memory. Current memory usage is %s and series num is %s. Please increase MAX_HEAP_SIZE in datanode-env.sh/bat, restart and create timeseries again. We want to guide users to use device template, so we change it to: Too many timeseries in memory without device template(current memory: %s, series num: %s). To optimize memory, DEVICE TEMPLATE is more recommended when devices have same time series. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6217) Change the hint msg while memory it enough to create more timeseries
Yuan Tian created IOTDB-6217: Summary: Change the hint msg while memory it enough to create more timeseries Key: IOTDB-6217 URL: https://issues.apache.org/jira/browse/IOTDB-6217 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian Previous error msg is: There are too many timeseries in memory. Current memory usage is %s and series num is %s. Please increase MAX_HEAP_SIZE in datanode-env.sh/bat, restart and create timeseries again. We want to guide users to use device template, so we change it to: Too many timeseries in memory without device template(current memory: %s, series num: %s). To optimize memory, DEVICE TEMPLATE is more recommended when devices have same time series. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6216) Change the hint msg while memory it enough to create more timeseries
Yuan Tian created IOTDB-6216: Summary: Change the hint msg while memory it enough to create more timeseries Key: IOTDB-6216 URL: https://issues.apache.org/jira/browse/IOTDB-6216 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian Previous error msg is: There are too many timeseries in memory. Current memory usage is %s and series num is %s. Please increase MAX_HEAP_SIZE in datanode-env.sh/bat, restart and create timeseries again. We want to guide users to use device template, so we change it to: Too many timeseries in memory without device template(current memory: %s, series num: %s). To optimize memory, DEVICE TEMPLATE is more recommended when devices have same time series. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6213) Change the hint msg while memory it enough to create more timeseries
Yuan Tian created IOTDB-6213: Summary: Change the hint msg while memory it enough to create more timeseries Key: IOTDB-6213 URL: https://issues.apache.org/jira/browse/IOTDB-6213 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian Previous error msg is: There are too many timeseries in memory. Current memory usage is %s and series num is %s. Please increase MAX_HEAP_SIZE in datanode-env.sh/bat, restart and create timeseries again. We want to guide users to use device template, so we change it to: Too many timeseries in memory without device template(current memory: %s, series num: %s). To optimize memory, DEVICE TEMPLATE is more recommended when devices have same time series. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6200) Change schema template to device template
Yuan Tian created IOTDB-6200: Summary: Change schema template to device template Key: IOTDB-6200 URL: https://issues.apache.org/jira/browse/IOTDB-6200 Project: Apache IoTDB Issue Type: Task Components: Core/Schema Manager Reporter: Yuan Tian Assignee: Yuan Tian Change all schema template to device template, to be compatible forwards, we need to keep the schema template, but in docs we will all use device template to replace schema template. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6199) Session automatically fetch all available DataNodes
Yuan Tian created IOTDB-6199: Summary: Session automatically fetch all available DataNodes Key: IOTDB-6199 URL: https://issues.apache.org/jira/browse/IOTDB-6199 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Yuan Tian To let user session still be alive while some nodes shut down in cluster, we need to save all available datanodes' urls in Session, if one failed to connect, we can try next node. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6184) Merge Sort finish one iterator too late.
[ https://issues.apache.org/jira/browse/IOTDB-6184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-6184: Assignee: yang caiyin > Merge Sort finish one iterator too late. > > > Key: IOTDB-6184 > URL: https://issues.apache.org/jira/browse/IOTDB-6184 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Labels: pull-request-available > Attachments: image-2023-10-10-18-22-07-777.png > > > There is a wrong implementationo in MergeSortOperator > !image-2023-10-10-18-22-07-777.png! > If the code break too late, the smaller value behind tsBlock won't be filled > in time, resulting in a wrong order. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6178) Call fsync after writing file
Yuan Tian created IOTDB-6178: Summary: Call fsync after writing file Key: IOTDB-6178 URL: https://issues.apache.org/jira/browse/IOTDB-6178 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: Yuan Tian Assignee: Yuan Tian Currently, lots of IO operations in IoTDB doesn't call fsync after doing writing which may cause file content lost if users restarting computer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6173) Change default encoder of INT32 and INT64 from RLE to TS_2DIFF
Yuan Tian created IOTDB-6173: Summary: Change default encoder of INT32 and INT64 from RLE to TS_2DIFF Key: IOTDB-6173 URL: https://issues.apache.org/jira/browse/IOTDB-6173 Project: Apache IoTDB Issue Type: Task Reporter: Yuan Tian Assignee: Yuan Tian We found that in most user cases TS_2DIFF has better compression rate than RLE for INT32 and INT64 type, so we change the default encoder of INT32 and INT64 from RLE to TS_2DIFF -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6171) NPE will be thrown while printing FI with debug on
Yuan Tian created IOTDB-6171: Summary: NPE will be thrown while printing FI with debug on Key: IOTDB-6171 URL: https://issues.apache.org/jira/browse/IOTDB-6171 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: 李伟豪 Attachments: image-2023-09-26-10-52-03-063.png, image-2023-09-26-10-52-18-340.png Change logback-datanode.xml from default info level to debug level, insert some data, and execute select * from root.**, you will get the following error msg: !image-2023-09-26-10-52-03-063.png! !image-2023-09-26-10-52-18-340.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6166) UDTFTimestampRepair cause OOM
Yuan Tian created IOTDB-6166: Summary: UDTFTimestampRepair cause OOM Key: IOTDB-6166 URL: https://issues.apache.org/jira/browse/IOTDB-6166 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Attachments: 问题2.zip The replay way can be found in the README.txt of the attachment. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6164) Can create illegal path through rest api
Yuan Tian created IOTDB-6164:
Summary: Can create illegal path through rest api
Key: IOTDB-6164
URL: https://issues.apache.org/jira/browse/IOTDB-6164
Project: Apache IoTDB
Issue Type: Bug
Reporter: Yuan Tian
Assignee: Yuan Tian
We can use the following command to replay this bug:
{code:java}
curl -H "Content-Type:application/json"/jso"Authorization:Basic
cm9vdDpyb290"yb290" -X POST
-'{"timestamps":[1635232143960,1635232153960],"measurements":["s3","===OPC接口机工作组0==TEST4"],"data_types":["INT32","BOOLEAN"],"values":[[11,null],[false,true]],"is_aligned":false,"device":"root.sg27"}'
http://127.0.0.1:18080/rest/v2/insertTablet {code}
===OPC接口机工作组0==TEST4 is not a legal path, we should use `` to include it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6160) while using ` in target path, select into will throw error
Yuan Tian created IOTDB-6160:
Summary: while using ` in target path, select into will throw error
Key: IOTDB-6160
URL: https://issues.apache.org/jira/browse/IOTDB-6160
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: Yuan Tian
Assignee: 李伟豪
Attachments: image-2023-09-18-15-42-42-379.png
Using the following sql, you will get the error msg.
{code:java}
insert into root.ods.`test_100#txt`(time, param1) values(now(),4);
select param1 into root.dwgraph.`predw$2547333405855956946$32`(abcd) from
root.ods.`test_100#txt`{code}
!image-2023-09-18-15-42-42-379.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6141) Optimize the large time range raw query performance
Yuan Tian created IOTDB-6141: Summary: Optimize the large time range raw query performance Key: IOTDB-6141 URL: https://issues.apache.org/jira/browse/IOTDB-6141 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2023-09-07-14-47-48-090.png, image-2023-09-07-14-51-04-689.png, iot-query.properties, iot-write.properties Use the iot-write.properties in attachment to generate data. Then use the iot-query.properties in attachment to test query performance, you can get the following result: !image-2023-09-07-14-47-48-090.png! After profiling the DataNode, we found that much time wasting in Array.growCapacity which can be totally avoided, because we can estimate the TsBlock size using page statistics. !image-2023-09-07-14-51-04-689.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6134) Fill statement field of show queries for inner schema fetch
Yuan Tian created IOTDB-6134: Summary: Fill statement field of show queries for inner schema fetch Key: IOTDB-6134 URL: https://issues.apache.org/jira/browse/IOTDB-6134 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2023-08-31-16-43-35-277.png Currently, our inner query like `fetch schema` won't display its sql while we show queries which may be confusing. !image-2023-08-31-16-43-35-277.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6115) Limit & Offset push down doesn't take effect while there exist null value
Yuan Tian created IOTDB-6115: Summary: Limit & Offset push down doesn't take effect while there exist null value Key: IOTDB-6115 URL: https://issues.apache.org/jira/browse/IOTDB-6115 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2023-08-16-13-56-22-334.png If there exists null value in any column, it seems that the offset and limit push down doesn't use the statistics to skip. !image-2023-08-16-13-56-22-334.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6112) Limit & Offset push down doesn't take effect while there exist time filter
Yuan Tian created IOTDB-6112: Summary: Limit & Offset push down doesn't take effect while there exist time filter Key: IOTDB-6112 URL: https://issues.apache.org/jira/browse/IOTDB-6112 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2023-08-14-14-27-17-784.png, image-2023-08-14-14-28-08-409.png We found that if we add `where time > 0`, the sql will be much slower which means the limit & offset filter push down doesn't take effect. !image-2023-08-14-14-28-08-409.png! !image-2023-08-14-14-27-17-784.png! However, when I remove the `where time > 0`, time costs will be about 0.2s -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6110) procedure_completed_evict_ttl's time unit is inconsistent with the source code
Yuan Tian created IOTDB-6110: Summary: procedure_completed_evict_ttl's time unit is inconsistent with the source code Key: IOTDB-6110 URL: https://issues.apache.org/jira/browse/IOTDB-6110 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Attachments: image-2023-08-10-16-57-07-017.png, image-2023-08-10-16-57-15-992.png In iotdb-common.properties, the comments said that its time unit is `s`, however in source code it's used as `ms`. !image-2023-08-10-16-57-15-992.png!!image-2023-08-10-16-57-07-017.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6109) While \r\n exist in NodeName, insert will fail
Yuan Tian created IOTDB-6109: Summary: While \r\n exist in NodeName, insert will fail Key: IOTDB-6109 URL: https://issues.apache.org/jira/browse/IOTDB-6109 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu Attachments: image-2023-08-10-16-52-31-254.png While \r\n exist in NodeName, insert will fail, however, as the user doc said, I can use `` to include that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6107) CQ can be created successfully but failed to execute
Yuan Tian created IOTDB-6107:
Summary: CQ can be created successfully but failed to execute
Key: IOTDB-6107
URL: https://issues.apache.org/jira/browse/IOTDB-6107
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: Yuan Tian
Assignee: Yuan Tian
Attachments: image-2023-08-10-14-45-51-946.png
Use the following sql, I can successfully create CQ, but this CQ actually
cannot pass the semantic check. While it's executed, it will throw exception.
{code:java}
CREATE CONTINUOUS QUERY cq1
BEGIN
SELECT count(s1)
INTO root.cq.d1_d2(count_s1)
FROM root.db.d1, root.db.d2
GROUP BY(10s), LEVEL=1
END
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6104) tmp directory won't be cleaned after udf query end
Yuan Tian created IOTDB-6104: Summary: tmp directory won't be cleaned after udf query end Key: IOTDB-6104 URL: https://issues.apache.org/jira/browse/IOTDB-6104 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Fix For: 1.2.2, master, 1.1.3 Attachments: image-2023-08-08-20-47-38-670.png While using udf to query, and when the memory is not enough, we will spill the data to disk. However when the query end, the tmp directory is not cleaned completely. !image-2023-08-08-20-47-38-670.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6096) M4 will output zero while meeting null
Yuan Tian created IOTDB-6096: Summary: M4 will output zero while meeting null Key: IOTDB-6096 URL: https://issues.apache.org/jira/browse/IOTDB-6096 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: data.zip, image-2023-08-03-14-30-14-936.png using the data in the attachment and runing a 1D1D IoTDB, then execute the following sql: ``` select M4(t21,’timeInterval'='20'),M4(t10,’timeInterval'='20') fronroot.ZYJ_test.test where time<=16908827389 and time>=16908827080 ``` !image-2023-08-03-14-30-14-936.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6049) Nested UDF function will throw memory not enough exception
Yuan Tian created IOTDB-6049: Summary: Nested UDF function will throw memory not enough exception Key: IOTDB-6049 URL: https://issues.apache.org/jira/browse/IOTDB-6049 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu Attachments: image-2023-07-05-17-00-08-497.png, image-2023-07-05-17-00-15-617.png Nested UDF function will throw memory not enough exception, but memory should be enough in such case, because there is not too mcuh data. !image-2023-07-05-17-00-08-497.png! !image-2023-07-05-17-00-15-617.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6012) Client receive The consensus group SchemaRegion[0] doesn't exist error
Yuan Tian created IOTDB-6012: Summary: Client receive The consensus group SchemaRegion[0] doesn't exist error Key: IOTDB-6012 URL: https://issues.apache.org/jira/browse/IOTDB-6012 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Reporter: Yuan Tian Assignee: Song Ziyang Attachments: SessionExample.java, image-2023-06-20-09-41-11-877.png Using GraalVM CE 22.3.1 as your jdk and then mvn clean package to get your distribution package. Execute the SessionExample in the attachment and you will get the error message: !image-2023-06-20-09-41-11-877.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5993) ConfigNode leader changing causes lacking some DataPartition allocation result in the response of getOrCreateDataPartition method
Yuan Tian created IOTDB-5993: Summary: ConfigNode leader changing causes lacking some DataPartition allocation result in the response of getOrCreateDataPartition method Key: IOTDB-5993 URL: https://issues.apache.org/jira/browse/IOTDB-5993 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: Yongzao Dan Attachments: image-2023-06-13-10-58-12-517.png, image-2023-06-13-10-58-35-694.png, image-2023-06-13-11-00-27-605.png We will get `Lacked some DataPartition allocation result in the response of getOrCreateDataPartition method` error message if confignode leader changing happens just after confirm leader done. !image-2023-06-13-11-00-27-605.png! !image-2023-06-13-10-58-12-517.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5963) Sometimes we may get out-of-order query result
Yuan Tian created IOTDB-5963: Summary: Sometimes we may get out-of-order query result Key: IOTDB-5963 URL: https://issues.apache.org/jira/browse/IOTDB-5963 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu Attachments: image-2023-06-02-09-11-28-986.png While using export-tsfile tool, we will see the following error: !image-2023-06-02-09-11-28-986.png! while means that there exists out-of-order data in our query result -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5815) NPE when using UDF to query
[ https://issues.apache.org/jira/browse/IOTDB-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-5815: Assignee: liaolanyu > NPE when using UDF to query > --- > > Key: IOTDB-5815 > URL: https://issues.apache.org/jira/browse/IOTDB-5815 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Liuxuxin >Assignee: liaolanyu >Priority: Major > Labels: pull-request-available > Fix For: master branch, 1.1.0 > > Attachments: image-2023-04-25-09-27-41-577.png > > > !image-2023-04-25-09-27-41-577.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5941) Same Column in one group by level query
Yuan Tian created IOTDB-5941: Summary: Same Column in one group by level query Key: IOTDB-5941 URL: https://issues.apache.org/jira/browse/IOTDB-5941 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: 李伟豪 初始化数据如下: insert into root.ln.wf01.wt01(timestamp,temp1)values(0,21); insert into root.ln.wf01.wt01(timestamp,temp1)values(360,22); insert into root.ln.wf01.wt01(timestamp,temp2)values(0,23); insert into root.ln.wf01.wt01(timestamp,temp2)values(360,24); insert into root.ln.wf01.wt02(timestamp,temp1)values(0,25); insert into root.ln.wf01.wt02(timestamp,temp1)values(360,26); insert into root.ln.wf01.wt02(timestamp,temp2)values(0,27); insert into root.ln.wf01.wt02(timestamp,temp2)values(360,28); insert into root.ln.wf01.wt03(timestamp,temp1)values(0,29); insert into root.ln.wf01.wt03(timestamp,temp1)values(360,30); insert into root.ln.wf01.wt03(timestamp,temp2)values(0,31); insert into root.ln.wf01.wt03(timestamp,temp2)values(360,32); 查询sql: select avg(temp1) from root.ln.wf01.wt03, root.ln.wf01.wt01 group by ([1970-01-01T08:00:00,1970-01-01T10:00:00),1h),level=2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5939) Flusing Task Timeout Detect Thread always use default timeout parameter as its timeout
Yuan Tian created IOTDB-5939: Summary: Flusing Task Timeout Detect Thread always use default timeout parameter as its timeout Key: IOTDB-5939 URL: https://issues.apache.org/jira/browse/IOTDB-5939 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Flusing Task Timeout Detect Thread should use timeout in session instead of default timeout parameter as its timeout. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5922) DeadLock in Memory Pool
Yuan Tian created IOTDB-5922: Summary: DeadLock in Memory Pool Key: IOTDB-5922 URL: https://issues.apache.org/jira/browse/IOTDB-5922 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu Attachments: result.txt -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5917) Refactor then package structure
[
https://issues.apache.org/jira/browse/IOTDB-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuan Tian reassigned IOTDB-5917:
Assignee: Yuan Tian (was: Alima777)
> Refactor then package structure
> ---
>
> Key: IOTDB-5917
> URL: https://issues.apache.org/jira/browse/IOTDB-5917
> Project: Apache IoTDB
> Issue Type: Task
>Reporter: Yuan Tian
>Assignee: Yuan Tian
>Priority: Major
>
> There are too many first-level packages module in IoTDB, we need to refactor
> it as following:
>
> move client-cpp, client-py, client-go, jdbc, session, cli, compile-tools,
> service-rpc, isession into {{iotdb-client}}
> move openapi, thrift, thrift-commons, thrift-confignode, thrift-influxdb,
> thrift-iot-consensu, thrift-mlnode into {{iotdb-protocol}}
> move subscription-api, udf-api, trigger-api, pipe-api, external-pipe-api,
> external-api into {{iotdb-api}}
> remove integration
> move flink-iotdb-connector, flink-tsfile-connector, grafana-connector,
> grafana-plugin, hadoop, hive-connector, spark-iotdb-connector, spark-tsfile,
> zeppelin-interpreter, influxdb-protocol into {{iotdb-connector}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5917) Refactor then package structure
Yuan Tian created IOTDB-5917: Summary: Refactor then package structure Key: IOTDB-5917 URL: https://issues.apache.org/jira/browse/IOTDB-5917 Project: Apache IoTDB Issue Type: Task Reporter: Yuan Tian Assignee: Alima777 There are too many first-level packages module in IoTDB, we need to refactor it as following: client: client-cpp, client-py, client-go thrift：thrift，thrift-commons，thrift-confignode，thrift-influxdb，thrift-iot-consensus，thrift-mlnode programming-api：subscription-api，udf-api，trigger-api，pipe-api，external-pipe-api，external-api integration: remove integration:flink-iotdb-connector，flink-tsfile-connector，grafana-connector，grafana-plugin，hadoop，hive-connector，spark-iotdb-connector，spark-tsfile，zeppelin-interpreter，influxdb-protocol -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5900) Put SessionIdleTime into IClientSession
Yuan Tian created IOTDB-5900: Summary: Put SessionIdleTime into IClientSession Key: IOTDB-5900 URL: https://issues.apache.org/jira/browse/IOTDB-5900 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian Assignee: Hongyin Zhang Attachments: image-2023-05-19-14-07-47-413.png All session related info should be put into IClientSession. !image-2023-05-19-14-07-47-413.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5874) enable_data_partition_inherit_policy doesn't take effect
Yuan Tian created IOTDB-5874: Summary: enable_data_partition_inherit_policy doesn't take effect Key: IOTDB-5874 URL: https://issues.apache.org/jira/browse/IOTDB-5874 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Reporter: Yuan Tian Assignee: Yongzao Dan Attachments: image-2023-05-15-09-39-00-493.png If we set enable_data_partition_inherit_policy to `true` and we create two successive time partition for one same device, the next time partition doesn't use the previous one's data region. !image-2023-05-15-09-39-00-493.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5864) Print failed to install snapshot warn log while restarting
Yuan Tian created IOTDB-5864: Summary: Print failed to install snapshot warn log while restarting Key: IOTDB-5864 URL: https://issues.apache.org/jira/browse/IOTDB-5864 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: Xinyu Tan Attachments: image-2023-05-11-15-28-57-190.png The write throughput is also very low all the time after restarting. !image-2023-05-11-15-28-57-190.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5860) Total Number of file is wrong
Yuan Tian created IOTDB-5860: Summary: Total Number of file is wrong Key: IOTDB-5860 URL: https://issues.apache.org/jira/browse/IOTDB-5860 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: Hongyin Zhang Attachments: image-2023-05-10-17-41-08-561.png Should not add the open_file_handlers or more exactly, we should not put open_file_handlers metric in this chart !image-2023-05-10-17-41-08-561.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5858) Metric doesn't display the schemaCache hit ratio
Yuan Tian created IOTDB-5858: Summary: Metric doesn't display the schemaCache hit ratio Key: IOTDB-5858 URL: https://issues.apache.org/jira/browse/IOTDB-5858 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: Hongyin Zhang Attachments: image-2023-05-10-11-57-21-727.png, image-2023-05-10-11-58-06-084.png Using arthas, we can see that schema cache hit ratio is more than 99%, but the metric panel shows to be zero. !image-2023-05-10-11-57-21-727.png! !image-2023-05-10-11-58-06-084.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5856) Sometimes confignode will not start successfully while usi iotd to deploy 3C3D
Yuan Tian created IOTDB-5856: Summary: Sometimes confignode will not start successfully while usi iotd to deploy 3C3D Key: IOTDB-5856 URL: https://issues.apache.org/jira/browse/IOTDB-5856 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: Xinyu Tan Attachments: image-2023-05-09-17-17-15-658.png The ConfigNode will throw the following exceptions: !image-2023-05-09-17-17-15-658.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5855) DataRegion leader Distribution is same as DataRegion Distribution
Yuan Tian created IOTDB-5855: Summary: DataRegion leader Distribution is same as DataRegion Distribution Key: IOTDB-5855 URL: https://issues.apache.org/jira/browse/IOTDB-5855 Project: Apache IoTDB Issue Type: Bug Reporter: Yuan Tian Assignee: Xinyu Tan Attachments: image-2023-05-09-16-55-30-205.png !image-2023-05-09-16-55-30-205.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5851) Using limit clause in show devices query will throw NPE
Yuan Tian created IOTDB-5851: Summary: Using limit clause in show devices query will throw NPE Key: IOTDB-5851 URL: https://issues.apache.org/jira/browse/IOTDB-5851 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu Attachments: image-2023-05-09-13-39-24-716.png, image-2023-05-09-13-39-52-032.png show devices root.ca.** limit 10 will throw the following exception: !image-2023-05-09-13-39-24-716.png! the detailed thread stack is: !image-2023-05-09-13-39-52-032.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5833) Concurrent bug caused by non-atomic operation in QueryExecution
Yuan Tian created IOTDB-5833: Summary: Concurrent bug caused by non-atomic operation in QueryExecution Key: IOTDB-5833 URL: https://issues.apache.org/jira/browse/IOTDB-5833 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2023-04-28-09-24-08-392.png !image-2023-04-28-09-24-08-392.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5831) Drop database won't delete totally files in disk
Yuan Tian created IOTDB-5831: Summary: Drop database won't delete totally files in disk Key: IOTDB-5831 URL: https://issues.apache.org/jira/browse/IOTDB-5831 Project: Apache IoTDB Issue Type: Bug Components: Core/Schema Manager Reporter: Yuan Tian Assignee: Yukun Zhou While dropping database and inserting into that database concurrently, I found that there may exist stale data region related directories in disk like in consensus sub directory and wal sub directory. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5830) WAL file size is not right
Yuan Tian created IOTDB-5830: Summary: WAL file size is not right Key: IOTDB-5830 URL: https://issues.apache.org/jira/browse/IOTDB-5830 Project: Apache IoTDB Issue Type: Bug Components: Core/WAL Reporter: Yuan Tian Assignee: Hongyin Zhang Attachments: image-2023-04-27-20-05-36-019.png, image-2023-04-27-20-05-45-373.png !image-2023-04-27-20-05-36-019.png! !image-2023-04-27-20-05-45-373.png! The actual wal size is less than 1GB, but the monitor says that it occupy more than 50GB which is also used by writing thread to judge whether to throttle insert rate. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5829) Query with limit clause will cause other concurrent query break down
Yuan Tian created IOTDB-5829: Summary: Query with limit clause will cause other concurrent query break down Key: IOTDB-5829 URL: https://issues.apache.org/jira/browse/IOTDB-5829 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Attachments: image-2023-04-27-20-01-33-737.png !image-2023-04-27-20-01-33-737.png! 这个异常是因为Thread-A正在做IO，然后被其他线程interrup了（这里的原因有很多，比如超时，或者下游limit完了，需要提前结束上游的scan任务），然后，JVM就会自动把这个FileChannel给close了；但是我们的文件句柄是共享的，这就意味着如果此时同时有Thread-B正在使用这个文件句柄，就会因为文件句柄被close而异常退出。。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5824) show devices with * cannot display satisfied devices
Yuan Tian created IOTDB-5824: Summary: show devices with * cannot display satisfied devices Key: IOTDB-5824 URL: https://issues.apache.org/jira/browse/IOTDB-5824 Project: Apache IoTDB Issue Type: Bug Components: Core/Schema Manager Reporter: Yuan Tian Assignee: Yukun Zhou Attachments: image-2023-04-26-15-23-52-166.png !image-2023-04-26-15-23-52-166.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5802) Query cannot perform after frequent FGCs
[ https://issues.apache.org/jira/browse/IOTDB-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-5802: Assignee: Yuan Tian > Query cannot perform after frequent FGCs > > > Key: IOTDB-5802 > URL: https://issues.apache.org/jira/browse/IOTDB-5802 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.1.0, master >Reporter: Liuxuxin >Assignee: Yuan Tian >Priority: Major > Fix For: 1.1.0 > > Attachments: image-2023-04-22-14-48-49-583.png, > image-2023-04-22-14-58-56-071.png > > > Using 3C3D deployment, perform query simulation load and write simulation > load. Through the monitoring panel, it is discovered that only one of the > three nodes is executing queries. After a period of time (4 days), the node > executing the queries experiences frequent FGCs, with CPU usage consistently > reaching 100%, and both write and query operations become unresponsive; the > other two nodes have no abnormalities, but the write traffic begins to > decline. After killing the query process, observe the monitoring panel of the > FGC-affected node, and about 10 minutes later, FGCs no longer occur, CPU > utilization drops below 40%, the write throughput starts to rise. And at this > time, any query from the query load executed through the CLI will result in > the error shown in the following figure. That's said, writing can recover > from FGCs, while query cannot. After 24 hours, the system cpu load is about > 40%, FGCs occur often, the write throughput is low, and query is still not > executable. > !image-2023-04-22-14-58-56-071.png! > > !image-2023-04-22-14-48-49-583.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5769) Offset doesn't take effect in some special case
Yuan Tian created IOTDB-5769: Summary: Offset doesn't take effect in some special case Key: IOTDB-5769 URL: https://issues.apache.org/jira/browse/IOTDB-5769 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian insert into root.sg.d(time, s1) values(1,1); select * from root.sg.d offset 98784247808; We only insert one row and the offset value is much larger than 1, so we should get an empty result set. However, we can still get one row now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5552) No permissions when a non-root user inserts data into a timeseries with illegal path
[ https://issues.apache.org/jira/browse/IOTDB-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-5552: Assignee: 李伟豪 (was: Hongyin Zhang) > No permissions when a non-root user inserts data into a timeseries with > illegal path > > > Key: IOTDB-5552 > URL: https://issues.apache.org/jira/browse/IOTDB-5552 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: Haonan Hou >Assignee: 李伟豪 >Priority: Major > Attachments: image-2023-02-17-18-21-36-717.png, > image-2023-02-17-18-48-41-530.png > > > !image-2023-02-17-18-21-36-717.png|width=556,height=422! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5638) Support case when syntax in IoTDB
[ https://issues.apache.org/jira/browse/IOTDB-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-5638: Assignee: LiYuheng (was: Yuan Tian) > Support case when syntax in IoTDB > - > > Key: IOTDB-5638 > URL: https://issues.apache.org/jira/browse/IOTDB-5638 > Project: Apache IoTDB > Issue Type: New Feature > Components: Core/Query >Reporter: Yuan Tian >Assignee: LiYuheng >Priority: Major > > https://apache-iotdb.feishu.cn/docx/J1ALd8eSaoC3YoxO9zkcKdWXnkd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5718) Time order bug while using align by device
Yuan Tian created IOTDB-5718: Summary: Time order bug while using align by device Key: IOTDB-5718 URL: https://issues.apache.org/jira/browse/IOTDB-5718 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: yang caiyin Attachments: image-2023-03-23-10-03-24-601.png 1C1D IoTDB change the following two configuration in iotdb-common.properties data_region_group_extension_policy=CUSTOM default_data_region_group_num_per_database=3 Then, execute the following sqls ``` insert into root.db.d1(time,s1) values(2018-08-30T08:00:01.000+08:00, 10); insert into root.db.d1(time,s1) values(2018-09-30T08:00:01.000+08:00, 10); insert into root.db.d1(time,s1) values(2018-10-07T08:00:01.000+08:00, 10); insert into root.db.d1(time,s1) values(2018-10-15T08:00:01.000+08:00, 10); insert into root.db.d1(time,s1) values(2018-10-25T08:00:01.000+08:00, 10); insert into root.db.d1(time,s1) values(2018-11-03T08:00:01.000+08:00, 10); insert into root.db.d1(time,s1) values(2018-11-13T08:00:01.000+08:00, 10); flush; ``` After inserting the data, you can execute the align by device query and see the wrong time ordering ``` select s1 from root.db.d1 align by device; ``` while we don't add align by device, the result is right. !image-2023-03-23-10-03-24-601.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5715) Improve the performance of query order by time desc
Yuan Tian created IOTDB-5715: Summary: Improve the performance of query order by time desc Key: IOTDB-5715 URL: https://issues.apache.org/jira/browse/IOTDB-5715 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian Fix For: 1.2.0 Attachments: data.zip We found that order time desc is much slower than order by time asc. We can use the data in attachment and start a 1C1D IoTDB to replay that. ``` select * from root.sg1.d1 where s1 != 1 order by time asc; select * from root.sg1.d1 where s1 != 1 order by time desc; ``` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5657) Limit does not take effect in last query
Yuan Tian created IOTDB-5657: Summary: Limit does not take effect in last query Key: IOTDB-5657 URL: https://issues.apache.org/jira/browse/IOTDB-5657 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu Attachments: image-2023-03-09-20-21-33-867.png !image-2023-03-09-20-21-33-867.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5643) Add REPLACE as a built-in scalar function
Yuan Tian created IOTDB-5643: Summary: Add REPLACE as a built-in scalar function Key: IOTDB-5643 URL: https://issues.apache.org/jira/browse/IOTDB-5643 Project: Apache IoTDB Issue Type: New Feature Reporter: Yuan Tian Assignee: liaolanyu https://apache-iotdb.feishu.cn/docx/N4EqdXba0o0UWhxlCxicNo2Bn3f -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5642) Add CONCAT as built-in scalar function
Yuan Tian created IOTDB-5642: Summary: Add CONCAT as built-in scalar function Key: IOTDB-5642 URL: https://issues.apache.org/jira/browse/IOTDB-5642 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu https://apache-iotdb.feishu.cn/docx/UXt7dnLIqoinjlxmiKycIVVHn0W -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5641) Add regexp_replace as built-in scalar function
Yuan Tian created IOTDB-5641: Summary: Add regexp_replace as built-in scalar function Key: IOTDB-5641 URL: https://issues.apache.org/jira/browse/IOTDB-5641 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: liaolanyu https://apache-iotdb.feishu.cn/docx/U18ZdSflLoHSfBxVO5OcpKB1njh -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5640) Make one pipeline be able to have one more drivers
Yuan Tian created IOTDB-5640: Summary: Make one pipeline be able to have one more drivers Key: IOTDB-5640 URL: https://issues.apache.org/jira/browse/IOTDB-5640 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Alima777 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5638) Support case when syntax in IoTDB
Yuan Tian created IOTDB-5638: Summary: Support case when syntax in IoTDB Key: IOTDB-5638 URL: https://issues.apache.org/jira/browse/IOTDB-5638 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian https://apache-iotdb.feishu.cn/docx/J1ALd8eSaoC3YoxO9zkcKdWXnkd -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5637) Add substr as built-in scalar function
Yuan Tian created IOTDB-5637: Summary: Add substr as built-in scalar function Key: IOTDB-5637 URL: https://issues.apache.org/jira/browse/IOTDB-5637 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Zhijia Cao https://apache-iotdb.feishu.cn/docx/JklEd4c58obZDOxx3l5cmCxanfg -- This message was sent by Atlassian Jira (v8.20.10#820010)
