lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] [Resolved] (LUCENE-4610) Implement a NoParentsAccumulator
Date Mon, 01 Jul 2013 20:47:20 GMT


Shai Erera resolved LUCENE-4610.

       Resolution: Implemented
    Lucene Fields: New,Patch Available  (was: New)

We have OrdinalPolicy.NO_PARENTS with a warning not to use it when a document will share few
categories with common ancestors. I don't think that at this point we should do anything more.
> Implement a NoParentsAccumulator
> --------------------------------
>                 Key: LUCENE-4610
>                 URL:
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/facet
>            Reporter: Shai Erera
>         Attachments: LUCENE-4610.patch
> Mike experimented with encoding just the exact categories ordinals on LUCENE-4602, and
I added OrdinalPolicy.NO_PARENTS, with a comment saying that this requires a special FacetsAccumulator.
> The idea is to write the exact categories only for each document, and then at search
time count up the parents chain to compute requested facets (I say count, but it can be any
> One limitation of such accumulator is that it cannot be used when e.g. a document is
associated with two categories who share the same parent, because that may result in incorrect
weights computed (e.g. a document might have several Authors, and so counting the Author facet
may yield wrong counts). So it can be used only when the app knows it doesn't add such facets,
or that it always asks to aggregate a 'root' that in its path this criteria doesn't hold (no
categories share the same parent).

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message