[
https://issues.apache.org/jira/browse/SOLR-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13138408#comment-13138408
]
Martijn van Groningen commented on SOLR-2863:
---------------------------------------------
bq. So faceting with group.truncate will only look at the content of the first
document in the group after the query/sort has been performed?
Yes. It will only have the most relevant document. What the most relavant
document is depends on your sort.
bq. To enable what I would expect Solr would need to re-sort the documents in
the group for each facet.query? There's no way I can specify the sort inside
the facet query to get this to happen?
There is no work around for this as far as I know. You can't sort inside a
facet.query, b/c it only counts.
bq. Does that mean this doesn't work for field facets either (until 'matrix
counts' are done)?
Until matrix facets have been implemented any facet type will have the same
problem.
> Solr 3.4 group.truncate does not work with facet queries
> --------------------------------------------------------
>
> Key: SOLR-2863
> URL: https://issues.apache.org/jira/browse/SOLR-2863
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 3.4
> Environment: Solr 3.4 on Windows Server 2008.
> Reporter: Ian Grainger
> Labels: facet, grouping, query, search, truncate
>
> When using Grouping with group.truncate=true, The following simple facet
> query:
> facet.query=Monitor_id:[380000 TO 400000]
> Doesn't give the same number as the nGroups result for the equivalent filter
> query:
> fq=Monitor_id:[380000 TO 400000]
> From the Wiki page: 'group.truncate: If true, facet counts are based on the
> most relevant document of each group matching the query.'
> If I turn off group.truncate then the counts are the same, as I'd expect -
> but unfortunately I'm only interested in the grouped results.
> Asked this question on the Solr-user mailing list and was told it is likely a
> bug by: Martijn Groningen.
> I'd be very interested in any workaround for this bug!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
