[
https://issues.apache.org/jira/browse/SOLR-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798147#action_12798147
]
Yonik Seeley commented on SOLR-1712:
------------------------------------
Also keep in mind that the docset used for faceting may not be the one used to
return results (this is true for multi-select).
And yes, if you still want the top 10 constraints *after* eliminating those
with count>=facet.maxcount, it makes distributed search *much* harder (and
probably makes future per-segment faceting harder too).
> option to supress facet constraints when count is == numFound
> -------------------------------------------------------------
>
> Key: SOLR-1712
> URL: https://issues.apache.org/jira/browse/SOLR-1712
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> It would be handy to have an easy option to suppress (on the server side) any
> facet contraint values whose count is the same as numFound (ie: filtering on
> that constraint would not reduce the result size)
> this should be a corollary to facet.mincount=1 and happen prior to
> facet.limit being applied.
> http://old.nabble.com/Removing-facets-which-frequency-match-the-result-count-to27026359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
