[
https://issues.apache.org/jira/browse/SOLR-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108517#comment-17108517
]
Christine Poerschke commented on SOLR-13289:
--------------------------------------------
Seeing the inclusion of {{minExactHits}} in the {{QueryResultKey}} made me
curious about caching effects e.g. would or wouldn't a minExactHits=100 request
make use of a minExactHits=1000 cache entry and/or would use of the cache
affect the "equal" vs. "greater than or equal" indication in the response --
https://github.com/cpoerschke/lucene-solr/commit/68042c52fa58dc1e4e61145b101b3877501b708d
shares what i have so far.
> Support for BlockMax WAND
> -------------------------
>
> Key: SOLR-13289
> URL: https://issues.apache.org/jira/browse/SOLR-13289
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
> Assignee: Tomas Eduardo Fernandez Lobbe
> Priority: Major
> Attachments: SOLR-13289.patch, SOLR-13289.patch
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> LUCENE-8135 introduced BlockMax WAND as a major speed improvement. Need to
> expose this via Solr. When enabled, the numFound returned will not be exact.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
