You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2018/05/18 10:03:00 UTC
[jira] [Commented] (IGNITE-7642) Ignite fails with OOM if query has
"NULLS LAST"
[ https://issues.apache.org/jira/browse/IGNITE-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480446#comment-16480446 ]
Andrew Mashenkov commented on IGNITE-7642:
------------------------------------------
H2 has an Issue #699: When using an index for sorting, the index is ignored when also using NULLS LAST/FIRST.
This issue is fixed in the latest h2-1.4.197 version.
Seems, we have to upgrade H2 dependency first.
> 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
> Fix For: 2.6
>
> 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)