[
https://issues.apache.org/jira/browse/SOLR-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787682#comment-16787682
]
Ishan Chattopadhyaya commented on SOLR-13289:
---------------------------------------------
Context: There were some discussions between Adrien and Hoss on LUCENE-8060 on
how to expose it on Lucene side.
bq. numFound=false , may be?
We can configure Lucene to provide a minimum threshold of numFound up to which
the counts will be exact (IOW, we can specify we need at correct counts up to
"at least 1000", say).
In terms of invoking it, I see two options:
# We can let the user specify this limit (as in this patch via "minExactHits")
or,
# just have a hardcoded value (e.g. 1000) and let the user pass numFound=false
to invoke it.
I feel the first option gives the expert user more control, whereas a novice
user need not care about any of this.
In any case, we can return this information as approxNumFound="1000+" or
approxNumFound="1215+" etc.
WDYT? [~hossman], [[email protected]], any thoughts?
> Support for BlockMax WAND
> -------------------------
>
> Key: SOLR-13289
> URL: https://issues.apache.org/jira/browse/SOLR-13289
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Major
> Attachments: SOLR-13289.patch
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
