[ https://issues.apache.org/jira/browse/LUCENE-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236257#comment-16236257 ]
Adrien Grand commented on LUCENE-8017: -------------------------------------- Indeed, only caching at the segment level is supported. bq. // no point cacheing this! (in MatchNoDocsQuery) For similar reasons as MatchAllDocsQuery I think we should return the core cache helper? For instance say the query is A OR B OR C and C rewrites to a MatchNoDocsQuery, it would still make sense to cache the BooleanQuery? > FunctionRangeQuery and FunctionMatchQuery can pollute the QueryCache > -------------------------------------------------------------------- > > Key: LUCENE-8017 > URL: https://issues.apache.org/jira/browse/LUCENE-8017 > Project: Lucene - Core > Issue Type: Bug > Reporter: Alan Woodward > Assignee: Alan Woodward > Priority: Major > Attachments: LUCENE-8017.patch, LUCENE-8017.patch > > > The QueryCache assumes that queries will return the same set of documents > when run over the same segment, independent of all other segments held by the > parent IndexSearcher. However, both FunctionRangeQuery and > FunctionMatchQuery can select hits based on score, which depend on term > statistics over the whole index, and could therefore theoretically return > different result sets on a given segment. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org