[BUILD-STABLE]: Job 'IoTDB/IoTDB-pip-new/master [master] [437]'
BUILD-STABLE: Job 'IoTDB/IoTDB-pip-new/master [master] [437]': Is back to normal.
[jira] [Created] (IOTDB-6276) Pipe: Add ConnectionTimeoutMs & Load Max TsFile Data Size for IOTDBLoadTsFileIT.testLoadWithMods
Sicheng Yu created IOTDB-6276: - Summary: Pipe: Add ConnectionTimeoutMs & Load Max TsFile Data Size for IOTDBLoadTsFileIT.testLoadWithMods Key: IOTDB-6276 URL: https://issues.apache.org/jira/browse/IOTDB-6276 Project: Apache IoTDB Issue Type: Bug Reporter: Sicheng Yu Assignee: Sicheng Yu Attachments: IOTDBLoadTsFileIT_testLoadWithMods.zip Question: - IOTDBLoadTsFileIT.testLoadWithMods fails to pass the CI, the client displays NPE and the logs show that TsFileWriterManager has been closed. - The reason is that the Load receiver is unable to persist the file fragments within the Thrift timeout, which causes the Load to advance to the second phase and close the TsFileWriterManager that is persisting at the receiver, resulting in an exception being thrown. Solution: - Increase IOTDBLoadTsFileIT.testLoadWithMods to test the Thrift Timeout time and the upper limit of Load file fragment size in the scenario. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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] [Assigned] (IOTDB-6274) Bug in Group by month
[ https://issues.apache.org/jira/browse/IOTDB-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-6274: -- Assignee: yang caiyin > Bug in Group by month > - > > Key: IOTDB-6274 > URL: https://issues.apache.org/jira/browse/IOTDB-6274 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Attachments: image-2023-12-21-18-01-42-411.png > > > # can't query with group by month + limit/offset > # Group by month calculate the wrong results. > # Can't use __endTime in GROUP BY TIME + ALIGN BY DEVICE > > The right way to calcute the time results in group by month should be > (startTime + count*MonDuration + nonMonDuration*count, endTime + > (count+intervalNum)*MonDuration + nonMonDuration*(count+intervalNum)] which > can't be accumulative. > Example(red is the right result): > !image-2023-12-21-18-01-42-411.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6274) Bug in Group by month
yang caiyin created IOTDB-6274: -- Summary: Bug in Group by month Key: IOTDB-6274 URL: https://issues.apache.org/jira/browse/IOTDB-6274 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Attachments: image-2023-12-21-18-01-42-411.png # can't query with group by month + limit/offset # Group by month calculate the wrong results. # Can't use __endTime in GROUP BY TIME + ALIGN BY DEVICE The right way to calcute the time results in group by month should be (startTime + count*MonDuration + nonMonDuration*count, endTime + (count+intervalNum)*MonDuration + nonMonDuration*(count+intervalNum)] which can't be accumulative. Example(red is the right result): !image-2023-12-21-18-01-42-411.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
