You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/08/13 10:49:01 UTC

[jira] [Created] (IGNITE-9256) SQL: make sure that fetched results are cleared from iterator when last element is fetched

Vladimir Ozerov created IGNITE-9256:
---------------------------------------

             Summary: SQL: make sure that fetched results are cleared from iterator when last element is fetched
                 Key: IGNITE-9256
                 URL: https://issues.apache.org/jira/browse/IGNITE-9256
             Project: Ignite
          Issue Type: Bug
          Components: sql
    Affects Versions: 2.6
            Reporter: Vladimir Ozerov
            Assignee: Sergey Grimstad
             Fix For: 2.7


In practice it is possible for user to forget to nullify Ignite's result set after iteration is finished. Or he may delay cleanup for some reason. 
The problem is that we hold the whole H2's result set inside our iterator even after all results are delivered to the user. 
We should forcibly close and then nullify all H2 objects once all results are returned. 

Key code pieces:
{{IgniteH2Indexing.executeSqlQueryWithTimer}} - how we get result from H2
{{H2ResultSetIterator}} - base iterator with H2 objects inside



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)