[
https://issues.apache.org/jira/browse/SOLR-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104816#comment-17104816
]
Tomas Eduardo Fernandez Lobbe commented on SOLR-13289:
------------------------------------------------------
bq. I agree with Ishan on not enabling this by default.
Agree, I intentionally left it to a separate Jira issue. I made a comment in
the PR.
bq. I know minNumFoundToBeExact is kinda long but it's more clear than the
counter-proposals and I don't expect people to be typing it often (thus "q" and
"fq" for example are justifiably super short).
Well "typing often", likely doesn't happen with any parameter, since this is
coded somewhere. But still, I think we don't need such verbosity here. My
personal favorite is still {{minExactCount}}
> 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
