[
https://issues.apache.org/jira/browse/SOLR-17037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-17037:
----------------------------------
Labels: pull-request-available (was: )
> LTR Queries don't use queryResultCache
> --------------------------------------
>
> Key: SOLR-17037
> URL: https://issues.apache.org/jira/browse/SOLR-17037
> Project: Solr
> Issue Type: Bug
> Components: contrib - LTR, ltr
> Affects Versions: 9.4
> Reporter: Doug Turnbull
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Before queries are placed in the query result cache, they get rewritten.
> Sometimes this rewriting happens in-place. The key used for the query result
> cache, has as one element, the query.
> For LTRQuery -> LTRScoringQuery, rewriting will change the cache key's
> original query. Thus when we insert using this key, it's not the same as
> subsequent queries that perform a lookup. So LTRQueries never benefit from
> the cache.
> A similar issue was resolved with general reranking queries by [~jbernste]
> SOLR-7689 - https://issues.apache.org/jira/browse/SOLR-7689
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
