[
https://issues.apache.org/jira/browse/IGNITE-17813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623113#comment-17623113
]
Stanislav Lukyanov commented on IGNITE-17813:
---------------------------------------------
Also, I kinda think this is not a blocker for beta. The case that doesn't work
is pretty straightforward (ORDER BY breaks if it sorts using a sorted index),
so it's easy to just call it out in release notes. Also, I suspect there is a
WA - just add a wrapping the original query with another one, like
{code:java}
select * from ( select * from T order by indexed_col ) order by indexed_col
{code}
So if you really need to get this query to run correctly (although slowly), you
can.
[~xtern] thoughts?
> Sql. Introduce sorted reducer for IndexScanNode
> -----------------------------------------------
>
> Key: IGNITE-17813
> URL: https://issues.apache.org/jira/browse/IGNITE-17813
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> This task is derived from IGNITE-17655 to reduce its scope.
> Currently, IgniteScanNode reads partition after partition which, obviously,
> breaks the sorting order. We need to introduce wrapping cursor, which accepts
> open cursors for every partition, and produce the sorted output.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
