[
https://issues.apache.org/jira/browse/SOLR-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658875#action_12658875
]
Ryan McKinley commented on SOLR-936:
------------------------------------
Are you talking about:
{code:java}
public FacetField getLimitingFields(long max)
{code}
If so, that is just a utility function that lets you filter out facets that
have fewer options that some number (typically getNumFound)
If you don't want filtered results, just that FacetField directly and call:
{code:java}
public List<Count> getValues();
{code}
> Facet Results - REST vs SolrJ
> -----------------------------
>
> Key: SOLR-936
> URL: https://issues.apache.org/jira/browse/SOLR-936
> Project: Solr
> Issue Type: Bug
> Components: clients - java, search
> Affects Versions: 1.4
> Reporter: Andrew Nagy
> Priority: Minor
> Fix For: 1.4
>
>
> There is a difference in the way Facet results are reported in SolrJ from the
> REST interface. In REST, if you apply a facet via the fq param, no matter
> what the count it is always reported back in the list of facets in the
> responses. However, with SolrJ - it only reports back facets that don't
> match the total number of documents. This is quite frustrating to deal with.
>
> The difference can be seen when ORing or ANDing in the fq param. When I or
> to facet values together, they come back in SolrJ since their counts don't
> match the total docs. But if I AND them together, they don't appear in the
> list. So then I need to munge in the applied fq values.
> Why the difference in behavior between REST and SolrJ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
