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

Markus Jelsma commented on SOLR-10952:
--------------------------------------

Ah, i understand. The cache is tucked away in SolrIndexSearcher so that is 
never going to work unless cache replay is passed through regular search 
handler and query component. Maybe QuerySenderListener could be of help to 
regenerate the cache instead, it seems to be passed through the core's 
execute().

> Exact*Stats are ignored due to query result cache
> -------------------------------------------------
>
>                 Key: SOLR-10952
>                 URL: https://issues.apache.org/jira/browse/SOLR-10952
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: search
>            Reporter: Mikhail Khludnev
>            Priority: Major
>
> the case is described at 
> https://issues.apache.org/jira/browse/SOLR-10824?focusedCommentId=16062814&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16062814
>  
> {quote}
> * search id:11, got it cached in query results.
> * add docs, commit
> * it triggers cache regeneration, this query is executed per every shard. 
> However, their scores are local only.
> * search id:11 again, got cache hit, retrieve local only scores. Ignore exact 
> stats, even they are properly distributed via GET_TERM_STATS
> {quote}
> the seed to reproduce {{-ea -Dtestcase=TestExactSharedStatsCache 
> -Dtests.method=test -Dtests.seed=EF21F7455842423F -Dtests.multiplier=2 
> -Dtests.slow=true -Dtests.locale=de-GR -Dtests.timezone=Etc/GMT-11 
> -Dtests.asserts=true -Dtests.file.encoding=UTF-8}}, note the test was fixed 
> by https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=7c44862 . So, 
> to reproduce, it needs to be rolled back. 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to