[
https://issues.apache.org/jira/browse/SOLR-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094032#comment-17094032
]
Tomas Eduardo Fernandez Lobbe commented on SOLR-13289:
------------------------------------------------------
The code in [the PR|https://github.com/apache/lucene-solr/pull/1456] is taking
shape, please take a look at it if you are interested in the change. Specially,
please take a look at the API. I decided to include in the response the
{{hitCountRelation}}, similar to what Lucene responds (which can be
{{EQUAL_TO}} or {{GREATER_OR_EQUAL_TO}}). I initially thought about just
including a boolean to say if the hit count was exact or an approximation, but
I decided to include the relation:
1) To be more precise
2) To be open to possible changes in Lucene, which could give more values to
this relation
I had to ignore a Javabin "forward compatibilty" test, since the binaries
change and break the test, however, I believe the changes are compatible
("forward" and "backward"). I left the current default of minExactHits to be
MAX_INT (count all) for now. I plan to have a new issue to have that discussion
separately.
> 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: Ishan Chattopadhyaya
> Priority: Major
> Attachments: SOLR-13289.patch, SOLR-13289.patch
>
> Time Spent: 50m
> 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
