[
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)
