[
https://issues.apache.org/jira/browse/SOLR-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Nagy reopened SOLR-936:
------------------------------
I am referring to the code in SolrJ that filters out any facets with the same
count as the total number of search results. This is different from the REST
interface.
See the bottom of:
http://svn.apache.org/viewvc/lucene/solr/trunk/src/solrj/org/apache/solr/client/solrj/response/FacetField.java?revision=724175&view=markup
Solrj filters out facet values where as the raw output from the REST interface
does not.
> 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.