[
https://issues.apache.org/jira/browse/SOLR-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3956:
---------------------------
Attachment: SOLR-3956.patch
After tracing down the problem with using facet.offset combined with
facet.limit<0 i started to rethink the wisdom of changing getFacetEntries to
treat negative numbers as "unlimited" it seemed more prudent to revise the
patch so that the the calling code in Solr passes Integer.MAX_VALUE when
facet.limit < 0, and update getFacetEntries to not have int overflow if
Integer.MAX_VALUE < offset+limit. (fixing other cases extreme cases beyond just
facet.limit < 0)
tests now all pass, but i'm running some more iterations in case i've tripped
something in other random tests.
> group.facet and facet.limit=-1 returns no facet counts
> ------------------------------------------------------
>
> Key: SOLR-3956
> URL: https://issues.apache.org/jira/browse/SOLR-3956
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 4.0
> Reporter: Mike Spencer
> Assignee: Hoss Man
> Attachments: SOLR-3956.patch, SOLR-3956.patch, SOLR-3956.patch,
> SOLR-3956.patch, SOLR-3956.patch
>
>
> Attempting to use group.facet=true and facet.limit=-1 to return all facets
> from a grouped result ends up with the counts not being returned. Adjusting
> the facet.limit to any number greater than 0 returns the facet counts as
> expected.
> This does not appear limited to a specific field type, as I have tried on
> (both multivalued and not) text, string, boolean, and double types.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
