[
https://issues.apache.org/jira/browse/IGNITE-26758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046998#comment-18046998
]
Kirill Anisimov commented on IGNITE-26758:
------------------------------------------
Additionally verified the {*}{{}}{*}{{{}{{SqlQuery}}{}}} execution path.
h4. What was added
* Reused the same test-only instrumentation
({{{}executeFieldsQueryHitCount(){}}} /
{{{}resetExecuteFieldsQueryHitCount(){}}}).
* Extended {{GridCacheQueryManagerExecuteFieldsQueryTest}} with
*SqlQuery-specific* coverage:
## {{SqlQuery}} with {{setLocal(true)}} on a single node
## {{SqlQuery}} with {{setLocal(false)}} on a 2-node grid, with keys selected
so that entries are primary on different nodes
h4. Result
In all {{SqlQuery}} scenarios the hit counter remains {*}0{*}. Therefore,
*{{qryResCache}} is not involved* in {{SqlQuery}} execution.
> Figure out what qryResCache is used for and where it is used
> ------------------------------------------------------------
>
> Key: IGNITE-26758
> URL: https://issues.apache.org/jira/browse/IGNITE-26758
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Anisimov
> Assignee: Kirill Anisimov
> Priority: Major
> Labels: cache, investigation
> Fix For: 2.18
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is a qryResCache module in our codebase, but it is not entirely clear
> what exactly it caches and what it is intended for. It is necessary to
> analyze its operation and determine whether it needs to be used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
