[ https://issues.apache.org/jira/browse/SOLR-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095150#comment-17095150 ]
Andrzej Bialecki commented on SOLR-13289: ----------------------------------------- IMHO the {{hitCountRelation}} vs {{numFound}} is jarring and at the first glance looks cryptic and unrelated to each other. I understand that this reflects the API naming in Lucene, but I think Solr could be much more user-friendly here and use a name that is both related to {{numFound}} and self-explanatory - perhaps {{numFoundPrecision}} or simply {{precision}}? After all, Solr doesn't use Lucene's {{totalHits}} name either, right? The enum name is also very long - in total this element adds 40 characters to the response for something that is a simple flag ... > 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: 1h 20m > 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