[
https://issues.apache.org/jira/browse/SOLR-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106021#comment-17106021
]
Tomas Eduardo Fernandez Lobbe commented on SOLR-13289:
------------------------------------------------------
[~dsmiley], I'm still debating myself on whether this is the best solution for
the bug you spotted:
https://github.com/tflobbe/lucene-solr-1/commit/9beaf4131e53f04651b9e6d9afba60192f348c73,
please take a look.
bq. I suggest minExactFound instead because it has the word "Found" which is
perhaps the most significant portion of "numFound".
I understand it's because of {{numFound}}, but It just sounds very weird to me
that the input parameter for the query carries the word "found".
> 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
