[ 
https://issues.apache.org/jira/browse/LUCENE-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565497#comment-13565497
 ] 

Michael McCandless commented on LUCENE-4715:
--------------------------------------------

base = ALL, comp = ALL_BUT; I disabled checking facet counts match in 
luceneutil because with ALL_BUT the dims have 0 count (expected) but with ALL 
they have the rolled up count.  Also, I ran on the 5 non-huge flat dims in 
luceneutil:
{noformat}
                    Task    QPS base      StdDev    QPS comp      StdDev        
        Pct diff
                HighTerm       18.91      (1.4%)       21.32      (2.2%)   
12.8% (   9% -   16%)
                 MedTerm       45.93      (1.2%)       54.08      (1.7%)   
17.7% (  14% -   20%)
                 LowTerm      101.51      (0.5%)      124.79      (1.4%)   
22.9% (  20% -   24%)
{noformat}
                
> Add OrdinalPolicy.ALL_BUT_DIMENSION
> -----------------------------------
>
>                 Key: LUCENE-4715
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4715
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/facet
>            Reporter: Shai Erera
>            Assignee: Shai Erera
>         Attachments: LUCENE-4715.patch
>
>
> With the move of OrdinalPolicy to CategoryListParams, 
> NonTopLevelOrdinalPolicy was nuked. It might be good to restore it, as 
> another enum value of OrdinalPolicy.
> It's the same like ALL_PARENTS, only doesn't add the dimension ordinal, which 
> could save space as well as computation time. It's good for when you don't 
> care about the count of Date/, but only about its children counts.

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