[ 
https://issues.apache.org/jira/browse/LUCENE-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael McCandless updated LUCENE-4885:
---------------------------------------

    Attachment: LUCENE-4885.patch

New patch, moving the count to FacetResultNode.

I'm sure it's possible to get this count for the TopKInEach case but I don't 
understand the code well enough so it's -1 for now.

Also ... I'm not sure this count really belongs in the FRN: it seems quite 
wasteful in the common case of single root and lots of children to have this 
unused int on each child node.  Or I guess the issue is that we don't have a 
separate class for the "leaf" vs for intermediate nodes.  I guess the wasted 
int doesn't usually matter, since you usually don't request too many children, 
and these classes are transient ...
                
> each FacetResult should return the facet equivalent of totalHits
> ----------------------------------------------------------------
>
>                 Key: LUCENE-4885
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4885
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>              Labels: newdev
>             Fix For: 5.0, 4.3
>
>         Attachments: LUCENE-4885.patch, LUCENE-4885.patch
>
>
> This is cheap to compute, since the TopKFRH already must visit all 
> non-zero-count ords under the FacetRequest.categoryPath.
> This can be useful to a front end, eg to know whether to present a "More..." 
> under that dimension or not, whether to use a suggester like LinkedIn's facet 
> UI, etc.

--
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]

Reply via email to