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

Vladimir Ozerov commented on IGNITE-5482:
-----------------------------------------

[~al.psc], I looked through {{GridMapQueryExecutor}} implementation, and IMO 
implementation of any cache doesn't look reasonable at the moment. The main 
problem is that currently we store the whole result set in memory 
({{IgniteH2Indexing#executeSqlQuery}}), which makes execution of heavy requests 
prone to OOME. It seems that we should rework our {{ResultSet}} handling in 
favor of "streaming" approach or so to make the whole SQL product more stable. 

When done, most of existing patch would have to be reworked.

> Implement basic caching of query results
> ----------------------------------------
>
>                 Key: IGNITE-5482
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5482
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 2.0
>            Reporter: Alexander Paschenko
>            Assignee: Alexander Paschenko
>              Labels: important
>             Fix For: 2.2
>
>
> Sergi suggested that we reuse results of the same queries running 
> simultaneously - i.e. if a query is being executed with the same arguments 
> and flags again and again, there's no need to do actual querying of data, 
> instead we can really run query once while other simultaneous runs will wait 
> for those results.
> This strategy will be implemented on MAP stage of distributed query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to