[
https://issues.apache.org/jira/browse/LUCENE-10438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497020#comment-17497020
]
Greg Miller commented on LUCENE-10438:
--------------------------------------
Interesting thought. So off the top of my head, it seems like this could be
useful when the user wants counts for specific values in the "browse" case? In
that situation, {{Weight#count}} for the requested value could be used. This
would require deferring the aggregation computation (i.e., we'd have to stop
eagerly computing aggregations during initialization). Is that sort of what
you're thinking [~jpountz] , or is there more to this that I'm not considering?
> Leverage Weight#count in lucene/facets
> --------------------------------------
>
> Key: LUCENE-10438
> URL: https://issues.apache.org/jira/browse/LUCENE-10438
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
>
> The facet module could leverage Weight#count in order to give fast counts for
> the browsing use-case?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
