[
https://issues.apache.org/jira/browse/IGNITE-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090104#comment-16090104
]
Alexander Paschenko commented on IGNITE-5482:
---------------------------------------------
[~vozerov]
1, 2, 4 - fixed
3 - added clear on cache destroy
5 - if we went with iteration, we'd do so on each update/remove, which would be
costly performance wise. Moreover, we can't tell the results that should be
left from those to be cleared.
6 - there's no list to copy unwrapped rows from, there's a ResultSet we run
back and forth in. If we unwrapped the whole result set, we'd double memory
consumption here.
7 - cache is cleared in {{GridMapQueryExecutor.ResultSetWrapper#release}} - the
last user of result set effectively removes it from map as needed.
> 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)
