[
https://issues.apache.org/jira/browse/SOLR-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658934#action_12658934
]
Andrew Nagy commented on SOLR-936:
----------------------------------
Yes - thanks - this does solve my problem.
In regards to the "Applied Facets" it might be nice to separate the list of
returned facets to a list of available facets and a list of "applied" facets.
What is driving this idea is my curiosity on how to build a list of facets that
uses checkboxes instead of links. How do I know if the checkboxes should be
checked or not with out saving some state information about what the user
clicked on. It would be nice if solr could do this for me by either flagging
the facets that are in my fq or by keeping them in a different list.
> 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.
