[
https://issues.apache.org/jira/browse/SOLR-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114398#comment-17114398
]
Christine Poerschke commented on SOLR-13289:
--------------------------------------------
{quote}{quote}would or wouldn't a minExactHits=100 request make use of a
minExactHits=1000
{quote}
It wouldn't. Right now, it's just using equal. We could improve this for sure,
that said, I'm wondering how useful that would be in practice? like, people
doing the same request in the same index with different minExactHits. While
certainly could happen, I'm not sure how common that is.
{quote}
I agree, say {{minExactCount=100}} and {{minExactCount=1000}} on the same index
might be uncommon but a query with a {{minExactCount=}} restriction being able
to use a cache entry from a query without a {{minExactCount=}} restriction
might be more interesting. Anyhow, I've speculatively opened
[https://github.com/apache/lucene-solr/pull/1530] – though perhaps a new ticket
would be clearer since this one is now closed.
> 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
> Fix For: master (9.0), 8.6
>
> Attachments: SOLR-13289.patch, SOLR-13289.patch
>
> Time Spent: 5.5h
> 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
