[
https://issues.apache.org/jira/browse/LUCENE-10325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17513729#comment-17513729
]
ASF subversion and git services commented on LUCENE-10325:
----------------------------------------------------------
Commit 77ccf2fb359ee926a3776ec4a78b2c0d95ee45fb in lucene's branch
refs/heads/branch_9x from Greg Miller
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=77ccf2f ]
LUCENE-10325: Add getTopDims functionality to Facets (#773)
Co-authored-by: Yuting Gan <44444710+yut...@users.noreply.github.com>
> Add getTopDims functionality to Facets
> --------------------------------------
>
> Key: LUCENE-10325
> URL: https://issues.apache.org/jira/browse/LUCENE-10325
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/facet
> Reporter: Greg Miller
> Priority: Major
> Time Spent: 8h 50m
> Remaining Estimate: 0h
>
> The current {{getAllDims}} functionality is really the only way for users to
> determine the "top" dimensions in a faceting field (i.e., get the top dims by
> count along with their top-n children), but it has the unfortunate
> side-effect of resolving all child paths for every dim, even if the user
> doesn't intend to use those dims. For example, if a match set contains docs
> relating to 100 different dims (and various values under each), but the user
> only wants the top 10 dims with their top 5 children, they can call
> getAllDims(5) then just grab the first 10 results, but a lot of wasted work
> has been done for the other 90 dims.
> It would be nice to implement something like {{getTopDims(int numDims, int
> numChildren)}} that would only do the work necessary to resolve {{numDims}}
> dims instead of all dims.
--
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
