[
https://issues.apache.org/jira/browse/SOLR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464658
]
J.J. Larrea commented on SOLR-106:
----------------------------------
+1 on direction, and based on a quick scan of the patch.
It could be sort=asc|desc|none rather than true|false, but I'm not sure whether
anyone would ever have a use for asc so it's probably not worth implementing.
Of course extending to caching the facet tallies would dramatically speed
paging. Perhaps both getFieldCacheCounts and getFacetTermEnumCounts should
return a Collection, which could be a BoundedTreeSet when sorting or a List
implementation when not, holding all the counts >= facet.mincount; then
getTermCounts could centralize the paging and response creation and provide an
object to (someday) cache. It would lose the mincount=0 optimization for
getFieldCacheCounts, but how many users are really going to want mincounts=0
unless the list is small and non-sparse in which case the optimization isn't a
big win anyway.
> new facet params: facet.sort, facet.mincount, facet.offset
> ----------------------------------------------------------
>
> Key: SOLR-106
> URL: https://issues.apache.org/jira/browse/SOLR-106
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Yonik Seeley
> Attachments: facet_params.patch
>
>
> a couple of new facet params:
> facet lists become pageable with facet.offset, facet.limit (idea from Erik)
> facet.sort explicitly specifies sort order (true for count descending, false
> for natural index order)
> facet.mincount: minimum count for facets included in response (idea from JJ,
> deprecate zeros)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
