[
https://issues.apache.org/jira/browse/SOLR-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104734#comment-17104734
]
Ishan Chattopadhyaya commented on SOLR-13289:
---------------------------------------------
{quote}Maybe we can have something shorter? {{minExactNumFound}}? I also like
{{minExactCount}}, which I feels sounds a bit better, but more disconnected
from {{numFound}}
{quote}
{{minExactFound}} or {{numFoundThreshold}}.
{quote}But my plan is to make the default value for {{minFoundHits}} a
configuration in solrconfig.xml
{quote}
I'm -1 to this. I think this should be left as an opt-in feature for now (i.e.
users should pass it in for every query). At a later point, we can standardize
it and make it a default.
> 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: 3h 40m
> 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
