[jira] [Commented] (IGNITE-17453) Calcite Engine: ORDER BY Optimization

["Aleksey Plekhanov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-17453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573788#comment-17573788 ] 

Aleksey Plekhanov commented on IGNITE-17453:
--------------------------------------------

[~liyuj], can you please check this issue on the master branch? I hope it was fixed by IGNITE-16013.

> Calcite Engine: ORDER BY Optimization
> -------------------------------------
>
>                 Key: IGNITE-17453
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17453
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.13
>            Reporter: YuJue Li
>            Priority: Critical
>             Fix For: 2.14
>
>
> 1.start a node;
> 2.create table:
> CREATE TABLE PI_COM_DAY
> (COM_ID VARCHAR(30) NOT NULL ,
> ITEM_ID VARCHAR(30) NOT NULL ,
> DATE1 VARCHAR(8) NOT NULL ,
> KIND VARCHAR(1),
> QTY_IOD DECIMAL(18, 6) ,
> AMT_IOD DECIMAL(18, 6) ,
> PRIMARYKEY (COM_ID,ITEM_ID,DATE1)) WITH"template=partitioned,CACHE_NAME=PI_COM_DAY";
> CREATE INDEX IDX_PI_COM_DAY_ITEM_DATE ON PI_COM_DAY(ITEM_ID);
>  
> 3.insert some data, for example, 1m;
> 4.execute sql:
> select * from pi_com_day order by item_id desc limit 10;
> normal.
> select /*+ QUERY_ENGINE('calcite') */ * from pi_com_day order by item_id desc limit 10;
> then OOM.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)