[
https://issues.apache.org/jira/browse/IGNITE-25530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-25530:
--------------------------------------
Fix Version/s: 3.1
> Sql. Explain. Confusing printout of Sort node
> ---------------------------------------------
>
> Key: IGNITE-25530
> URL: https://issues.apache.org/jira/browse/IGNITE-25530
> Project: Ignite
> Issue Type: Bug
> Components: sql ai3
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the printout of {{Sort}} node looks like this:
> {code}
> Sort
> collation: [C1 ASC, C2 ASC]
> offset: 5
> fetch: 30
> est: (rows=35)
> {code}
> Both {{offset}} and {{fetch}} attributes are presented in the plan, but
> unlike Limit node, those attributes has slightly different semantic: they are
> summed up to calculate number of rows to store in memory and hence return
> when sorting is over.
> I believe it would be better to either get rid of {{offset}} attribute and
> report only {{fetch}} or implement proper semantic for {{fetch-offset}} pair
> so it matches the {{Limit}} node.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
