[
https://issues.apache.org/jira/browse/SOLR-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085441#comment-14085441
]
Hoss Man commented on SOLR-6319:
--------------------------------
bq. It's been years since I wrote that, but IIRC the thinking was that over
requesting when sorting by index was probably not worth it. It's a judgement
call, and shouldn't be categorized as a bug (if I'm understanding this issue
correctly).
I don't know how it could be considered "not a bug" ... did you look at the
steps to reproduce that i posted?
it's trivial to generate queries where facet.mincount>1 combined with small
facet.limit counts won't produce results even when results exist.
the comment "Overrequesting can help a little here, but not as much as when
sorting by count." seems like an understatement.
> if mincount > 1, facet.field needs to overrequest even if facet.sort=index
> --------------------------------------------------------------------------
>
> Key: SOLR-6319
> URL: https://issues.apache.org/jira/browse/SOLR-6319
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Hoss Man
>
> Discovered this while working on SOLR-2894. the logic for distributed
> faceting ignores over requesting (beyond the user specified facet.limit) if
> the facet.sort is index order -- but the rationale for doing this falls apart
> if the user has specified a facet.mincount > 1
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
