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

Shai Erera commented on LUCENE-4715:
------------------------------------

Mike and I have been testing some aspects of this issue - we should test some 
others too and paste all the results here. Here are the scenarios:

*ALL_BUT_DIMENSION*

This should be better than ALL, since it encodes half the ordinals for flat 
dimensions.
The test would be to index all flat dimensions with ALL (trunk) vs ALL_BUT 
(patch) and compare times.

*Per-Dimension Rollup*

This should be better for when you need to rollup counts for a small dimension 
(saves iterating on a large counts array).
The test would be to:

* Index all dimensions (flat + hierarchical), so the counts[] is big (2.5M 
entries)
** Index Date in its own CLP in both cases, the idea is to generate a big 
taxonomy
* Query with a FacetRequest Date/
* Trunk would do the full traversal, patch would do the per-dim rollup and 
hopefully should be better

*Per-Dimension OrdinalPolicy*

The only advantage here is that it lets you index under the same CLP dimensions 
with different OrdinalPolicy settings.
To compare, we'd need to index with trunk the dimensions as ALL or NO, vs patch 
which can mix between ALL and NO 
(we can discard ALL_BUT) for this test.
                
> Add OrdinalPolicy.NO_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