[ https://issues.apache.org/jira/browse/IGNITE-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-7642: ------------------------------------ Labels: sql-stability (was: ) > Ignite fails with OOM if query has "NULLS LAST" > ----------------------------------------------- > > Key: IGNITE-7642 > URL: https://issues.apache.org/jira/browse/IGNITE-7642 > Project: Ignite > Issue Type: Bug > Components: sql > Affects Versions: 2.3 > Reporter: Mikhail Cherkasov > Priority: Major > Labels: sql-stability > Fix For: 2.7 > > Attachments: OrderByNullsLastTest.java > > > I have an index for "a" filed of "A" type and the following SQL works fine: > SELECT * FROM A ORDER BY a LIMIT 0 + 50 > > but as soon as I added "NULLS LAST" it starts to fail with OOM error: > SELECT * FROM A ORDER BY a NULLS LAST LIMIT 0 + 50 > However for both queries, EXPLAIN says that it the uses index, I don't see > why it should fail, but looks like ignite tryes to load all memory into heap > and sort there, and this leads to OOM. > > A reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)