[jira] [Commented] (IOTDB-6335) Redundant rows when using GROUP BY TIME with LIMIT
[ https://issues.apache.org/jira/browse/IOTDB-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851489#comment-17851489 ] yang caiyin commented on IOTDB-6335: After analysis, the problem occurs due to the bug in limit/offset push down to GroupBy parameter. In the following logic, we want to calculate the new startTime after skip some points, but if size is smaller the size calculated, startTime will be negative which leads to problem. !image-2024-06-03-11-26-32-473.png! > Redundant rows when using GROUP BY TIME with LIMIT > -- > > Key: IOTDB-6335 > URL: https://issues.apache.org/jira/browse/IOTDB-6335 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Query >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Attachments: image-2024-06-03-11-26-32-473.png > > > When using {{{}GROUP BY time + LIMIT{}}}, if the number of {{LIMIT}} exceeds > the number of existing time intervals, it will generate excess time intervals. -- 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-6335) Redundant rows when using GROUP BY TIME with LIMIT
yang caiyin created IOTDB-6335: -- Summary: Redundant rows when using GROUP BY TIME with LIMIT Key: IOTDB-6335 URL: https://issues.apache.org/jira/browse/IOTDB-6335 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: yang caiyin Assignee: yang caiyin When using {{{}GROUP BY time + LIMIT{}}}, if the number of {{LIMIT}} exceeds the number of existing time intervals, it will generate excess time intervals. -- This message was sent by Atlassian Jira (v8.20.10#820010)