[
https://issues.apache.org/jira/browse/SOLR-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658874#action_12658874
]
Jayson Minard commented on SOLR-936:
------------------------------------
I see what Andrew is talking about.
The difference is this:
Solrj returns a list of further refinements, so it strips out anything that
would not further reduce the set. It says, if the facet count == the total
document count, don't return it in the list of further refinements.
Whereas the raw response obviously has not yet stripped it.
So Solrj could probably use a list of facets that are not further refinements
if it is interesting for users of the API to have those. They don't make sense
as possible new refinements but they do make sense in that they exist and some
people care that they exist in the resulting data.
> 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.
